People who have upgraded their repository code since revision 4282
probably have spurious checksums in their repositories now. Sorry,
folks -- I didn't detect the lossage before, because I made a typo in
svn_fs__rep_undeltify() which allowed 'make check' to pass (see the
correction below).
The problem was: when a representation was created, it was initialized
with the checksum for the empty string (which is correct, as far as it
goes). But checksums are not yet kept up-to-date as reps acquire
data, so it became invalid the first time the rep was changed -- and
the code failed to detect this, because of the missing 'return' in
svn_fs__rep_undeltify().
I committed a fix for this just now, in revision 4297. The fix is to
(temporarily) store a checksum of all zeros for new reps. This is the
magical "always succeed" checksum in the filesystem code, so it's
functionally equivalent to not having a checksum there at all, which
is fine until the checksum updating is finished.
I hope the number of people affected by this is minimal. If you're
one of the unfortunates, you'll start getting checksum mismatch errors
when you access certain files. The solution is to dump your
repository using the old svnadmin, and load with the new one. Very
sorry for the inconvenience; please post to dev if this solution
doesn't work, or if you have other problems.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 8 23:51:56 2003