Re: svn Checksum error

My guess is that your locally checked out copy of the files are corrupted. I ran into something like this when I rebuilt a repository and accidentally renumbered it by tossing out null-affect revisions.

One fast workaround is to check out the old repository to a new loation, and then do this to compare the existing file contents.

    #/crown/admin/sql > diff -ur . [new-project-dir] --exclude=\.svn

If it's more than a few files, then you can do this to copy your changes on top of your newly checked out directory.

    #crown/admin/sql > find . -name .svn -prune -o -type f -exec /bin/cp {} [new-project-dir]/{} \;

Does that make sense?
  ----- Original Message -----
  From: Jerry.Sommerville@crown.com
  To: users@subversion.tigris.org
  Sent: Tuesday, April 25, 2006 2:00 PM
  Subject: svn Checksum error

  We have been using Subversion with no problems on RH 4 with Windows XP Clients until we had this error doing a commit Subversion. The following was the response from Subversion:

  #/crown/admin/sql >svn status baanjobstats.sql
  M baanjobstats.sql
  #/crown/admin/sql >svn commit -m"Change application lock select to include orphan locks"
  Sending sql/baanjobstats.sql
  Transmitting file data .svn: Commit failed (details follow):
  svn: Base checksum mismatch on '/trunk/app/crown/admin/sql/baanjobstats.sql':
     expected: 25900ac0f4c47c66a019ca853767ff64
       actual: 87dc0aa8de41e37479ad5fc552519b55

  We have tried a "cleanup" with no results. What do we do to correct this problem?

  Jerry Sommerville
  UNIX Administrator
  Crown Equipment Corp.
  www.crown.com
Received on Fri Apr 28 13:51:31 2006