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

Re: Re: working copy locked - problems with 1.7.1

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 1 Dec 2011 20:46:23 +0000

On 1 December 2011 20:24, Colin Cole <colin.cole_at_subzero.com> wrote:
> When you run cleanup, you get the same error. When you run release lock, it says there's nothing to release.

If the working copy is locked and cleanup won't fix it then I'm afraid
it needs a fresh checkout. Did you get this WC by upgrading a 1.6 WC?
If so you may find a fresh checkout better as the upgrade process is
not as good as it could be. If not then you should report this on the
subversion users mailing list as it is a problem inside the subversion

Release lock is about a different sort of lock, i.e. gettign a lock in
the repository to prevent others from committing. The locked WC is
talking about local locks (like filesystem locks) to ensure WC
integrity. It's a somewhat overloaded term in Subversion and
frequently causes this confusion.

PS. Please quote some context in your replies.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-12-01 21:46:28 CET

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