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

unable to checkout repository after import (ERROR: XML data was not well-formed)

From: sprite <ml_at_5prite.com>
Date: 2003-07-27 16:31:08 CEST

Hi,

I have been using subversion for a bit of time, and it works pretty well
for me, until I bumped into this problem.

I created a fresh repository using svnadmin create command, and then I
did an svn import to import a bunch of files into the new repository,
the import process went fine without any errors. However, the repository
did not checkout, the checkout process was interrupted with an error,
like this:

[...]
A gaim/logs/100796647.log
svn: XML data was not well-formed
svn: not well-formed (invalid token) at line 3

Initially I bumped into this problem using a build which dated back to
mid-June. I suspected that this problem may has been fixed in the newest
release, but it is still reproducable using 0.26.0

The file names does not contain any i18n characters, however, the file
contents has an hybrid of Big5 and UTF-8 characters.

Somebody from IRC recommends me to check the contents of .svn in the
working copy. I did the check and in the partial working directory, a
file named .svn/log seems suspecious, since it contains a bunch of
backspace (\b) characters, here is an example:

<mv
   dest=".svn/props/8n&quot;^H18837.log.svn-work"
   name=".svn/tmp/props/8n&quot;^H18837.log.svn-work"/>

may be this is the cause of the problem, or my be not, I am not sure.

I have tried to import only the file directly before the error
(100796647.log), checkout does not produce any errors.

Thanks for your time for looking into my problem.

-- Alan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 28 04:13:23 2003

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

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