Charles Bailey <bailey@newman.upenn.edu> writes:
> I've recently started using svn (1.1.3 built under Mac OS X 10.3), and
> in early testing have tripped over a problem this error:
>
> svn: Malformed XML: not well-formed (invalid token) at line 5988
This sounds like a problem in a .svn/entries or .svn/log file
somewhere in your working copy, perhaps due to a bug whereby
Subversion may be failing to properly escape some XML-sensitive
filenames or something.
If you can narrow this down to a data set that still reproduces the
bug, but that you'd be willing to share, that'd be terrific. Failing
that, if you can find the .svn/entries or .svn/log file with the
problem, and show it to us, that would be great.
Thanks for the report,
-Karl
> Here're the details:
>
> 0. Repository created with "svnadmin create"; no mods other than permissions
> 1. Populated from client machine (with a bunch of prefs files) using
> svn import <path> svn+ssh://<server>/<rpath>
> with LANG and LC_CTYPE set to "en_US.UFT-8" on both machines
> (without which
> I see "can't recode" errors); this succeeds without complaint
> 2. Attempt to retrieve files back to client using
> svn co svn+ssh://<server>/<rpath> <new-local-root>
> grinds away for a while, then falls over with
> A <new-local-root>/Library/Preferences/Deneba/User Dictionary
> A <new-local-root>/Library/Preferences/Deneba/CVULg.set
> A <new-local-root>/Library/Preferences/Deneba/CVAppData.set
> svn: Malformed XML: not well-formed (invalid token) at line 5988
> 3. If I cd down into .../Deneba and run "svn cleanup", it succeeds,
> but trying to
> cleanup .../Preferences yields
> svn: In directory ''
> svn: Can't copy '.svn/tmp/text-base/TrueType Font Editor
> Prefs.svn-base' \
> to 'TrueType Font Editor Prefs.4.tmp': No such file or directory
>
> Since Googling for the "Malformed XML" error yields some mention of
> Unicode issues, and I'd stumbled over svn's requirement for custom
> LANG/LC_CTYPE settings above, I wondered whether this was also a
> Unicode-related problem. There are a couple files in the repository
> with non-ASCII characters in their names, but none of them are close
> (in collating sequence) to the last files checked out, and a scan of
> the .../Preferences/.svn/log* doesn't turn up any problems with these
> files. FWIW, "svn list svn+ssh://<server>/<rpath>" also works fine.
>
> If this is pure thick-headedness on my part, pointers to TFM/TFMLA
> happily accepted. If not, I'd appreciate any hints as to where I
> might best look next. I'm willing to give the current HEAD version a
> try, too, if Knowledgeable Folks think the issue's likely been fixed
> already.
>
> Thanks.
>
>
> --
> Regards,
> Charles Bailey < bailey _at_ newman _dot_ upenn _dot_ edu >
> Newman Center at the University of Pennsylvania
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 16 19:46:08 2005