The file in the directory that keeps track of what you have checked out, when, what revision, and from where, has gotten corrupted somehow, for that particular file.This is no more dangerous or critical than the normal odd file problem, and can be because of various problems, like a subversion program dying mid-change, power-disruption, etc. One possible explanation for that would be disk corruption. 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.To edit your working copy, you just use Net Logo like always.
: Subversion 1.7 implements a new working copy approach which centralises the meta data, and it now has a single directory at the root of your working copy.
If that doesn't work you need to do a fresh checkout.
Something has gotten out of sync or has become corrupt, and because it's in your BASE directory, unless you are confident tinkering with this, you're probably better off deleting the parent of the directory and then perform an update.
I chose "revert" for the file, with no other modifications to the files, and things returned to normal. In Intelli J IDEA I was able to make a copy of the file, then go into the project and delete the file in question, then commit successfully.
Error: Commit failed (details follow): Error: Checksum mismatch for Error: 'C:\sss\sss\trunk\xxxx\.svn\text-base\svn-base'; expected: Error: '3cee96f580409a1711a47541a07860dd', actual: 'a5fc0f8819b88bf32ab38d4c9a6b0654' Error: Try a 'Cleanup'.We use the We are going to copy the repository folder (which is on the server on campus) to a new working-copy folder (on your personal computer).