Re: Broken SVN revision paths encoding
From: Dominik Psenner <dpsenner_at_apache.org>
Date: Tue, 28 Jul 2015 21:40:42 +0200
Thanks Bert for your answer. I've used the latest tortoisehg which used to
https://bitbucket.org/tortoisehg/thg/wiki/libsvn
The server on the other ends dates back to 2011. I believe it is something
For the completeness of the story let me outline what happened:
Beforehand, as you might have guessed I am using hg as my local svn client
I've copied some random files that had to be versioned from a network share
We're now unable to svn log, nore the build/test environments and we have
Cheers
Subversion's clients properly encode characters to utf-8 as far as we know,
Bert
Sent from Surface
*From:* dpsenner_at_apache.org
Hi there,
Somehow I was able to commit a file with a broken filename encoding and now
svn: E130003: The REPORT response contains invalid XML (200 OK)
However, in wireshark I can see this coming in (stripped to the interesting
<S:log-item>
<S:added-path>foo\344.file</S:added-path>
</S:log-item>
The clients svn is not the latest, but a newer version does not work either:
>svn –version
svn, version 1.8.10 (r1615264)
compiled Aug 10 2014, 15:48:46 on x86-microsoft-windows
Any good ideas how we can bring the repository back to be fully functional?
Cheers
|
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.