Re: Question about locking file and problem with Updating

On 27.01.2014 23:42, B Hatcher wrote:
> I have had the same problem since updating to:
> TortoiseSVN 1.8.4, Build 24972 - 64 Bit , 2013/11/24 11:15:39
> Subversion 1.8.5, -release
> apr 1.4.8
> apr-util 1.5.2
> serf 1.3.2
> OpenSSL 1.0.1e 11 Feb 2013
> zlib 1.2.8
>
> Older tortoise clients on our network do not exhibit this problem.
>
> I didn't realize what was happening for a while, but recently noticed that when I execute the 'SVN Update' command, any files that I had executed 'SVN Get Lock...' for are no longer recognized by my file browser as locked. When querying the repository using 'SVN Repo-browser' the lock column still indicates that they are locked by me.
>
> The only way for me to "re-get" the lock is to execute 'SVN Get Lock...' and select 'Steal the locks', as Andrzej pointed out.
>
> I agree, I believe this to be a bug - it is inconsistent with the prior behavior of the 'SVN Update' command.

I can't reproduce this.
If I get the lock and run update, my working copy still has the lock and
I can release the lock without stealing or breaking it.
Of course, if the file I have the lock on is updated because someone
else changed it, then the lock already *is* broken and then of course I
don't have it anymore.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3072202
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].