I've got mine on my laptop, dev server, and production server, and all are (generally) up-to-date.If the repository gets corrupted you shouldn't hyperventilate knowing at least the latest rev of your data is in multiple places.A way you can make the checksum of the base file no longer match the saved checksum is if you edit the base file stored in .svn/.
You can do a grep (inadvisable) to find the expected (abcd1234) checksum string in revs, or do the following: Step 2: Rejiggering Step 3: Restoration Again, this is just what *I* did, and if you're not comfortable doing it, try one of the other links for alternatives.
MF Reverted /home/moovida/rcpdevelopment/WORKSPACES/jgrassudig33workspace/eu.hydrologis.jgrass.charting.jfreechart.libs/META-INF/MANIFEST.
Client Exception: Checksum mismatch while updating 'D:\WWW\Project\.svn\text-base\svn-base'; expected: '3f9fd4dd7d1a0304d8020f73300a3e07', actual: 'cd669dce5300d7035eccb543461a961e' The easiest way to fix it (if you don't have many changes) is to copy your changes to another directory, delete the directory where your project is checked out, and checkout the project again.
Then copy your changes back in (don't copy any folders) and commit, and continue. One blog post with the "just checkout the entire repo again and then copy files" solution claimed that their text editor was "automatically" editing files inside the folder but I know that's not the case for me since I have that folder excluded from any global search functionality...
It seems to be a bug in SVN (plenty of which have hit me in the past); if this is truly a better CVS I can't imagine how terrible CVS must have been.