BUG: TSVN1.5: Base checksum mismatch after get lock including an update

Hello,

I posted this already on the TSVN-dev-list and Stephan asked me
to post it here again and pointed me to
http://subversion.tigris.org/servlets/BrowseList?list=users&by=thread&from=653886
which may be the same bug:

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.

Ronny

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-22 20:40:36 CEST