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

Re: Malformed XML error

From: Kamin Whitehouse <kamin_at_eecs.berkeley.edu>
Date: 2004-01-26 11:52:35 CET

Thanks Erik, but I didn't use cvs2svn.py, I just did a "svnadmin create"
and "svn import" (the link might have been a red herring). Any other clues?

Erik Huelsmann wrote:
> Hi Kamin,
>>svn: Malformed XML: not well-formed (invalid token) at line 3
>>that is a pretty cryptic error message to me, does anybody have any
>>other clues? On this weg page-->
>> <-- it looks like I'm getting this error because a binary file was
> How nice you found my patch! :-)
> No, the error probably comes from cvs2svn.py. Did you use it to create your
> repository? If you did, then do you have any file names with non-ascii
> characters in their names?
> Applying that patch to your cvs2svn.py will fix that problem.
>>uploaded as a normal file when I imported and svn couldn't decode it
>>properly as I was checking out. If that's it, how do I fix that?
>>Otherwise, what could it be?
>>The file being downloaded was a .ppt (powerpoint) file (as were several
>>other files in the same directory which were imported and checked out
>>properly). If I do a svn cleanup I get the same error again. I'd
>>rather not check the whole repository in from scratch again because it
>>took about 10 hrs to import on my external USB1.0 hard drive.
> It is not the downloaded file which is the problem. Subversion does not make
> a difference between binary and text files (except for diff operations). The
> problem is - probably - that the encoding of the file name was not utf8...
> which unfortunately might mean that you will have to re-import using
> cvs2svn.py again....
> bye,
> Erik.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 26 19:53:30 2004

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.