Re: Subversion migration problems

"C. Michael Pilato" <cmpilato@collab.net> said:
> If I were you, I'd update to 0.36.0 -- else, you're in for at least
> one more dump/load in the future (we changed the repository format in
> 0.34.0).

I just tried a load/verify into a 0.36.0 repository. However, I'm still
getting checksum errors:

    * Verified revision 387.
    * Verified revision 388.
    * Verified revision 389.
    * Verified revision 390.
    svn: Checksum mismatch on rep '40t':
       expected: a69e82ef100f59f61c42b5ae29e67327
       actual: 25fe5e08dfce08fce2712861e7cfca1b

I have a question though. I don't know if the original dump'd database
database is corrupted or not (like I said, I'm getting non-identical dumps).
But regardless of that, should loads report an error about the dump as it's
reading? Instead of loading a corrupted database only to find out about it on
a verify/checkout?

On a side note, it'd be really cool if someone implemented an ECC algorithm for
the dumps. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 16 17:39:28 2004