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

Re: problem with svnsync and repository locks...

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 06 Jan 2011 08:34:37 -0500

On 01/06/2011 03:16 AM, Karl Heinz Marbaise wrote:
> Hi,
>
> may be i misunderstand a thing but have you implemented the lock-hooks as
> well to replicate the locks to the slave ? If i understand your explanation
> well you haven't ...
>
> svnsync doesn't replicate lock to slaves...
>
> excerpt from the Subversion book:
> ------
> The only thing we've left out here is what to do about locks. Because locks
> are strictly enforced by the master server (the only place where commits
> happen), we don't technically need to do anything. Many teams don't use
> Subversion's locking features at all, so it may be a nonissue for you.
> However, if lock changes aren't replicated from master to slaves, it means
> that clients won't be able to query the status of locks (e.g., svn status -u
> will show no information about repository locks). If this bothers you, you
> can write post-lock and post-unlock hook scripts that run svn lock and svn
> unlock on each slave machine, presumably through a remote shell method such
> as SSH. That's left as an exercise for the reader!
> --------

Sadly, the book offers hope where today there is very little. See
http://subversion.tigris.org/issues/show_bug.cgi?id=3457, which I composed
well after writing the aforementioned book section. :-(

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2011-01-06 14:35:37 CET

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