[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: Dave Lawrence <dlawrence_at_ad-holdings.co.uk>
Date: Fri, 09 May 2008 16:48:28 +0100

Stefan Küng wrote:
> 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'.
>
> Stefan
>

More info:
1) Can't reproduce this using the above command line sequence
2) Can't reproduce on a test repository using file:///
3) CAN reproduce running a test repository on svnserve 1.4.5 on Cygwin
4) Our main server (where I discovered this) is Apache with svn 1.3.1 on
Linux

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-09 17:49:07 CEST

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