Re: SVNSYNC: Locked file on deleted branch with svnsync

On Tue, 30 Jan 2007, David Glasser wrote:
> Subject: Re: SVNSYNC: Locked file on deleted branch with svnsync
> 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.
>

OK, I think maybe you think I'm comitting changes to the slave
repository????

No, I have the httpd on the slave re-directing commits to the master
repository as Justin Erenkrantz suggested back a month or so ago.

That's why I'm trying to figure out what went wrong. I did just delete
the bug-327 branch yesterday (no errors) and today I noticed that the
mirror as not synced up and when I went to do it manually I got the error
above...so, SOMETHING went wrong but I don't know what.

Thanks!

--
David Wayne Summers        "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  0B44 B118 85CC F4EC 7021  1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org