SVN - Checksum mismatch while updating

Question

When I try to update some files from Subversion, I get the error:

org.tigris.subversion.javahl.ClientException: 
Checksum mismatch while updating \'D:\\WWW\\         


        

Answer 1

I had a similar error and fixed as follows:

(My 'fix' is based on an assumption which may or may not be correct as I don't know that much about how subversion works internally, but it definitely worked for me)

I am assuming that .svn\text-base\import.php.svn-base is expected to match the latest commit.

When I checked the file I was having the error on , the base file did NOT match the latest commit in the repository.

I copied the text from the latest commit and saved that in the .svn folder, replacing the incorrect file (made a backup copy in case my assumptions were wrong). (file was marked read only, I cleared that flag, overwrote and set it back to read only)

I was then able to commit successfully.

Answer 2

had a similiar issue on a server but the SVN directory was very large , didn't want to delete and resync so I just made a copy of the files locally and then deleted them. When update succeeded and added files back in.

Answer 3

To resolve this follow following steps:

1. Open the entries file located in .svn directory where you are getting the error.
2. Find the entry for the file giving error and replace the expected value with actual value in error.
3. Now synchronize and try to update.

If it still does not work. Try these. Its just a workaround though:

1. Delete the file from your system.
2. Delete the entry of the file from entries file. (Starting from the name of the file till the special characters).
3. Now Synchronize and update the file.

This will get latest version of file from repository and all conflicts will be resolved.

Answer 4

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 .svn folders) and commit, and continue.

Answer 5

In case you are using SVN 1.7+ there is a workaround described here.

Just to recap:

1. Go to the folder with the file causing problems
2. Execute command svn update --set-depth empty (note: this will delete your files, so make a copy first!)
3. Execute command svn update --set-depth infinity

Answer 6

My solution was:

1. Execute svn cleanup from file system
2. Switch to another branch
3. Solve conflicts
4. Switch to the "problematic" branch
5. Execute cleanup from Spring Tool Suite
6. Execute Project Update