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

Re: Locked; Already Locked

From: Ben Fritz <fritzophrenic_at_gmail.com>
Date: Mon, 21 Oct 2013 08:40:20 -0500

On Sun, Oct 20, 2013 at 5:35 PM, Geoff Field <Geoff_Field_at_aapl.com.au> wrote:
> From: Simon Large
> Sent: Saturday, 19 October 2013 1:46 AM
> On 18 October 2013 15:16, John W. (Jack) Cane wrote:
> Entire folder tree is getting errors when trying to update or commit:
> Error : working copy (folder\file name) locked
> Error: (folder\filename) already locked
> Could you please show me how to clear this.
> Have you tried running Cleanup?
> Simon
> For commit:
> -----------
> Cleanup won't necessarily work if the files are actually locked when committing.
> Jack, is it possible that the files are locked by somebody else, or that you've locked them in another working copy? (Or that they've been locked somewhere that no longer exists?)
> I've been there myself. Often the only real way to clear this is to check "Steal the locks" in the "Get Lock" dialog.
> Either that, or (actually a more team-focussed approach) find who has the locks and ask them to release the locks.

But from the error message, that is NOT the kind of lock we're looking
at. See http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html#svn.advanced.locking.meanings
. Only files can be locked. You cannot lock the working copy or
directory with an "svn lock" command.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-21 15:40:46 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.