[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bug: Base checksum mismatch

From: Ronny Voelker <ronny.voelker_at_elaxy.com>
Date: Tue, 27 May 2008 13:34:27 +0000 (UTC)


I posted this already on the TSVN-dev-list and Stephan asked me
to post it on the SVN-user-list, which I did.
Because nobody answered, I'm trying it here:

when using a new TortoiseSVN1.5 against an svn-server v1.4, a Commit fails, when
one of the modified files has the needs-lock-property set and was updated while
requesting the lock.

Receipt to reproduce the behaviour:

Client: TortoiseSVN1.5.0-RC2 on WindowsXP
Server: svn 1.4.6 (Apache or svnserver) on WindowsXP or Linux

Create one repository (R) containing a file (F) with
the property needs-lock set.
Create two up-to-date working-copies of R (WC1,WC2).

Cd to WC1.
   TSVN-Get Lock for F.
   Modify F.
   TSVN-Commit F.

Cd to WC2.
   TSVN-Get Lock for F.
      TSVN: Locking failed because a newer version exits!
             Do you want to update and try again?
      Click Yes.
   View F (notice, that changes from last commit are missing).
   TSVN-Update F.
   View F again (changes from last commit are still missing).
   Modify F.
   TSVN-Commit F.
      TSVN: Commit failed:
            Base checksum mismatch in file...

Only TSVN has the update-while-getting-lock feature, so I dont know, how to
reproduce it in SVN.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-27 15:35:01 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.