2012/5/31 Aaron Turner <synfina...@gmail.com>: > I keep on getting this error: > > svn: Checksum mismatch while updating 'interfaces.lookup'; expected: > '2c21f93c8639901a28056a507aa54deb', actual: > '97c86da543f396d636e960e46dec7280' > > on the same file over and over again. I've blown away my working copy > of the repo and re-checked out and the problem goes away for a while > and then returns. > > Trying to understand two things: > > 1. What causes this and how I can prevent it from happening in the future? > > 2. Is there an easier way then blowing away my WC and re-checking out to fix > it? >
1. One well-known (broken) scenario when checksum mismatch error can occur is: when there is a pre-commit hook on the server that modifies the data. (Whatever is changed by the hook cannot be propagated back to the client that makes the commit). That is the reason why one should not change data in a pre-commit hook. 2. Another known cause is if something modifies "pristine" copies of files on your system (the *.svn-base files inside of ".svn" directory). In that case the pristine files will not match the data stored at server. That is exactly the error that checksum check is designed to catch. 3. I do not see anything remarkable in changelog for later versions of 1.6.x [1], albeit the following one fixed in 1.6.17: * fix datastream corruption during resumed transfer in ra_serf (r1154733) What HTTP library you are using in your configuration? Neon or serf? Neon is the default one in 1.6.x. Subversion is usually built with both (as displayed in its "svn --version" output). [1] http://svn.apache.org/viewvc/subversion/branches/1.6.x/CHANGES?view=markup Best regards, Konstantin Kolinko
