@Update: See post 2011/01/17/what-really-caused-my-svn-checksum-mismatch-problem for final solution
Have been struggling with svn checksum mismatch problem which is annoying, but no show stopper due to the problem being possible to solve by workarounds as described in this blogpost glob.bushi.net.nz/…/subversion-checksum-mismatch-easy-workaround/
But still, I needed to figure out what the root cause was, and it turned out that the Perl search/replace was the sinner.
Issuing the command
perl -pi -e ‘s#ojdbc14_10.2.0.2.jar#ojdbc6_11.1.0.7.0.jar#g’ `find . | grep jdbc.xml`
then verifying the change by looking at the file using VI. But when issuing
svn status
svn was not able to see any changes. Then I added a xml-comment describing the change, saving and then svn commit I got the checksum error. After doing the workaround and then editing the file all manually, not issuing the Perl-command…voila, no problem. Have not been able yet to figure out why svn don’t like Perl search/replace changing the file…not sure if the -pi -e could be causing the problem, but I’m quite sure it has been accepted before.









