I'm attempting to fix a person's repository and was surprised to find out that
svnadmin dump/verify aren't working as expected. In this particular case,
there was a bad text rep in an FSFS repository (it was pointing to the wrong
location, possibly contains the wrong size, and/or instructions). However,
there looked like a spot where it was supposed to end, so I adjusted the
length of the text rep to match... but didn't touch the md5sum. Ran
'svnadmin verify'. No problems. Ran 'svnadmin dump'. No problems. Checked
out that particular revision (note, the path has been obfuscated):
svn: Checksum mismatch for 'xxxx/yyy/zzzz/mylibrary.lib'; expected:
'34cf6e811bb3bbe0f5cc25e55c0bc82b', actual:
'6c51abaf8a5fdddf56d7a2ffb23c5a46'
I expected that if we were creating full dumps (not incremental, not delta
dumps) that the md5sum would be computed and verified for each file. The
same with svnadmin verify.
Was this the intended behavior?
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 10 12:11:40 2005