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

Re: Teaching svnadmin to remove orphaned locks (Was: [CONTRIB] remove-zombie-locks.py, workaround for Issue #2507)

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-01-16 01:34:38 CET

On Mon, Jan 15, 2007 at 11:01:04AM -0800, Daniel Rall wrote:
> > >I'd rather we try to make it impossible to have orphaned locks in the
> > >first place :-) Is that a hard problem?
> >
> > Any repo of mainly non-mergable data that uses a 'svn:needs-lock on all
> > files' model is extremely likely to have these orphaned locks. There
> > needs to be a way to clean old/existing repositories. Of course
> > remove-zombie-locks.py can do this now, it's a question of whether this
> > is such a core problem that it should be built into svnadmin or not.
> Hmm, I've been wondering the same thing as Malcolm. Why don't
> operations which could cause orphaned locks -- 'delete', 'move' (?),
> etc. -- check whether the target and child paths have any of the lock
> properties set on them, and take the appropriate action?

That's right - I'd rather we fix the problem than incorporate a function
into svnadmin that we have to maintain for all time, especially since we
have this great new contrib script that looks like it does everything we


  • application/pgp-signature attachment: stored
Received on Tue Jan 16 01:35:35 2007

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