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

Re: Cleanup needed after failed update

From: Andreas Krey <a.krey_at_gmx.de>
Date: Tue, 12 Jun 2012 13:24:56 +0200

On Tue, 12 Jun 2012 12:26:34 +0000, Johan Corveleyn wrote:
...
> > - BUT I cannot update again, I have to cleanup first!
>
> This seems normal too. Before doing anything, 'svn update' will lock
> the working copy (to prevent any concurrent svn actions from messing
> with it while it's updating). If 'svn update' fails midway through,
> the locks will be left.

I'd say, that depends. If svn dies horribly via core dump or being
'kill -9'ed, or the whole machine losing power, then ok.

But here it is a failure that svn itself detects and handles, and
this handling should IMHO include releasing the lock after any
other necessary cleanup. (After all, that running svn instance
still knows that it is its lock, unlike us who then need to
run 'svn cleanup'.) If 'svn up' can't know how to handle,
how should 'svn cleanup' later?

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2012-06-12 13:25:35 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.