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

Re: [PATCH] Improve reporting WC is locked/busy ('run cleanup')

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 14 Jul 2011 09:39:14 -0400

On Thu, Jul 14, 2011 at 9:36 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Thu, Jul 14, 2011 at 12:58:24PM +0100, Julian Foad wrote:
>> When the WC is locked we may (depending on the timing) see:
>>   $ svn up -q & svn up -q
>>   svn: E155004: Working copy '/home/...' locked.
>>   svn: E155004: '/home/...' is already locked.
>>   svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
>> details)
> What always bothered me about this message is that it does not
> explain the most likely reason why the working copy may be locked.
> Namely that another client is currently accessing the working copy,
> such as some GUI client performing background operations.
> The message currently implies that the only course of action is
> to run cleanup, but this is precisely the wrong thing to do if another
> client is performing an operation that will take a bit of time.

In my experience (with WC-1) that is never the cause of the message.
9 times out of 10 the problem is that the .svn folder has been removed
by some build process and the other is that some previous process
crashed and left locks behind.

Mark Phippard
Received on 2011-07-14 15:39:48 CEST

This is an archived mail posted to the Subversion Dev mailing list.