[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svnsync 1.8.0 fails if there is a non-printable characters in the commit message

From: olli hauer <ohauer_at_gmx.de>
Date: Mon, 24 Jun 2013 19:30:11 +0200

svnsync 1.8.0 fails if there is a non-printable characters in the commit message

Error message:
svnsync: E000022: Safe data 'MFC r251249, r251251, r251252, r' was followed by non-ASCII byte 24: unable to convert to/from UTF-8

No issue with svnsync 1.7.10 (neon based)

Parts of the file (synced with svnsync 1.7.10)

$> cat $repo/db/revprops/251/251614
...
MFC r251249, r251251, r251252, r2512, r251254 and r251515:

$> more $repo/db/revprops/251/251614
...
MFC r251249, r251251, r251252, r^X2512, r251254 and r251515:

$> hexdump -C $repo/db/revprops/251/251614
...
00000070 31 2c 20 72 32 35 31 32 35 32 2c 20 72 18 32 35 |1, r251252, r.25|

Culprit is the hex(18) sign.

--
olli
Received on 2013-06-24 19:30:53 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.