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

Re: SVNSYNC: Locked file on deleted branch with svnsync

From: David Glasser <glasser_at_mit.edu>
Date: 2007-01-30 20:18:10 CET

On 1/30/07, David Summers <david@summersoft.fay.ar.us> wrote:
> > Which repository?
>
>
> Oh, sorry. On the master repository. I just checked, and the slave
> repository has a whole lot more directorieses in the db/locks directory
> than the master (which again is strange) and when I did the "svnadmin
> lslocks /path/to/repository" on the slave it listed all the locked files.

Aha. Yeah, running the replay on the master doesn't interact with
locks at all, but on the mirror it is just doing an ordinary commit,
and so locks will mess it up. Just delete them with svnadmin rmlocks.
 In general, you should not be doing any sort of commit or locking
operation to svnsync mirrors; the notes/svnsync.txt file recommends
using a hook to prevent commits by users other than svnsync, and
perhaps it should also recommend not allowing any locks.

> > Manually editing files inside the db/ directory is never a good idea.
>
> True. But sometimes if you know and understand what you are doing then
> it is OK. In this case it doesn't seem to be good to mess around with
> that stuff.

That's true, but probably best for a last resort only.

--dave

-- 
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 30 20:18:24 2007

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