On 8/14/07, Stuart Roebuck <stuart.roebuck@ed.ac.uk> wrote:
> I'm running across a problem dumping and re-loading an existing svn
> repository which contains file names with '0x0d' characters.
>
> This problem has been experienced by others and is documented on a
> number of blogs and wikis including...
>
> <http://wincent.com/knowledge-base/Repository_migration>
>
> Nobody appears to have found a good solution to what appears to be a
> straight-forward bug: if the '0x0d' characters shouldn't be accepted
> by SVN they should not be in the dump of an existing SVN repository.
I do understand the problem, but leaving out the 0x0d characters is no
option, as the dump should be an exact copy of what is in your
repository.
What would be better is if you had a tool which would help you resolve
the situation with the dump better. The course of action taken by
Wincent is a bit drastic, I'd say, because others have written tools
to manipulate dumpfiles, maybe one of those supports mangling
filenames.
First and foremost, what you're seeing might be a bug in Subversion.
How did your repository get into this state? Which version was used to
create it, which versions were used to commit to it? Has the
repository been served and accessed with non Subversion WebDAV
clients? What other version information can you provide us with?
> I've looked through the reported issues on the issue tracker and
> can't find an entry for this issue. So this is my buddy-finding
> attempt.
The more information we can get, the better we can target the issue to
be filed. I hope you can help us.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 14 14:13:36 2007