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

Re: checkout / update problem: svn: Malformed XML: not well-formed (invalid token) at line ...

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 20 Aug 2013 12:38:40 +0100

markbeezhold <mark.beezhold_at_att.net> writes:

> Issue 2730 needs to be re-visited!!!
> (http://subversion.tigris.org/issues/show_bug.cgi?id=2730)
> I relocated an SVN repository, and shortly thereafter began seeing the
> "Issue 2730" problem.
> What a "PAIN"... Every time I do an "svn commit," the log-file inserts the
> same non-ASCII characters into the user-name value along with a valid
> user-name. I have to do an "svnadmin setrevprop" to fix the incoming
> version's "svn:author" property, and edit the update's log-file to remove
> the non-ASCII characters.
> Most lately, something has become so messed-up, that SVN adds a file, then
> breaks because of the the mal-formed XML problem, and then refuses to accept
> the file it had just added. Even the --force option does not help... I
> cannot break out of this cleanup/update cycle, now, no matter what I try.

If you have log files then you are using a 1.6 client which is unlikely
to get fixed. The 1.8 client will probably handle things better.

There is a problem with non-XML characters affecting some operations,
I've raised http://subversion.tigris.org/issues/show_bug.cgi?id=4415

Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2013-08-20 13:39:18 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.