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

Ronny Voelker wrote:
> Hello,
>
> 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...
>
> For me this looks like a SVN-bug, but because only TSVN has the
> update-while-getting-lock feature, I have no idea how to reproduce it in SVN.
> That's why I'm posting it here.

http://subversion.tigris.org/servlets/BrowseList?list=users&by=thread&from=653886

Maybe you can report this again on the list? Since I can't reproduce
this here (don't have a pre-1.5 server ready), you're the one who should
report this.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net