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

Re: Bug: get lock with update breaks working copy

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 09 May 2008 17:08:18 +0200

Dave Lawrence wrote:
> To reproduce
> - update to revision on a file, update to the previous rev (let's call
> this rev 1, and assume HEAD is r2)
> - get lock -> "locking failed becuase a new version exists! Do you want
> to update and try again?"
> - Click yes
> Now the file is locked, but
> - The entries file still states that the file is at r1
> - The base file is as per r1
> - The working copy is as per r1
> Now if I do "update", the entries file is updated but the others are not.
> While I suspect this is a generic SVN problem rather than TSVN, I can't
> find a command line equivalent of this scenario - svn lock simply fails
> on an out of date file, it doesn't offer the update.
> 100% reproduceable with the latest nightly.

svn up file -r1
svn lock file
-> lock fails
svn up file
svn lock file

That's basically the sequence TSVN executes when you do the 'lock'.


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

Received on 2008-05-09 17:08:31 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

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