[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: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 14 Jul 2011 15:36:23 +0200

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.

So I would like this to say, maybe:

  svn: E155004: Working copy '/home/...' locked.
  svn: E155004: '/home/...' is already locked.
  svn: another Subversion client might be modifying the working copy at the moment; please try again later
  svn: if there is no other client run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Received on 2011-07-14 15:37:01 CEST

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