Clever Geek Handbook

Can't resolve Subversion 1.7 checksum mismatch error on upgrade

My Subversion 1.7.17 working folder is unhappy with a certain file, but cannot update it. Any attempt to update gives me the same error, even if I delete the file or delete the directory: 
Updating 'trunk/src/Makefile':
svn: E155017: Checksum mismatch for '/Volumes/project/dev/torc/trunk/src/Makefile':
   expected:  78ee11ff73f3b68c903db838b6667ec3
   recorded:  62bbbf4362958e3fd42470650d5b4eb6

I have read SVN - Checksum Mismatch on Update , and its two main solutions are to change .svn/entries

or delete and restore the directory. There is nothing useful about the top-level file .svn/entries

in section 1.7, and deleting and restoring the directory did not solve my problem. Does anyone have any other suggestions?

+3


source to share


4 answers


This may be an older question, but I would like to share how I resolved it without checking out the entire (multiple GB) repository. I hope this helps people who have the same problem.

I am using TortoiseSVN for Windows.



  • Open Repo-Browser by right-clicking on the parent folder of the file and choosing TortoiseSVN> Repo-Browser
  • In the repo browser, right click on the file, select Update Item in Editor
  • From the Refresh Depth drop-down menu, select Exclude , click OK. This removes the checksum entry from the local repository database.
  • Delete the file in explorer (trashbin), update the repository
  • Go back to the Update Item In Editor section, for Update Depth, select Working Copy
  • Update the repository again

Everything should be normal.

+5


source


In my case, the problem was a corrupted .svn / pristine folder, and I solved it by replacing that whole folder with another from a clean working copy.

I am using SVN 1.8.4 under Cygwin.



Steps to fix the problem:

  • backups, if any
  • back up .svn / pristine (in the root wc folder).
  • prepare link wc: ('svn commit / revert; svn update')
  • replace .svn / pristine with the problem with one of the wc link
  • enjoy :)
+1


source


I am using Subversion 1.7+ (Tortoise) client and solved this problem in two simple ways:

and. svn update --set-depth = empty

b. svn update --set-depth = infinity

As a reminder, step a will delete all your local files in that folder! So keep in mind to make a copy first.

+1


source


It's easy. Copy the problem file to your computer in a different directory. Delete the problem file from the computer and fix it. Make svn on the server. Now put the file back in the inicial directory, do the append and commit. And make a new svn on the server. Ask his solution.

0


source






More articles:


All Articles