Cool. Looks like the props on the destination are:
svn:sync-currently-copying = 1
svn:sync-from-url = <svn url>
svn:sync-from-uuid = <source repo uuid>
svn:sync-last-merged-rev = <whatever rev>
then there's the locking and stuff. So, would it hurt to prepare the
current master for when I switch it to mirror by setting
svn:sync-from-url, svn:sync-from-uuid? I'd probably set the uuids the
same between master and slave to make things more transparent to
users. That hurt anything in svnsync?
On 9/14/06, Garrett Rooney <firstname.lastname@example.org> wrote:
> On 9/14/06, Mark <email@example.com> wrote:
> > I am curious aboyut this new feature. I have a custom solution in
> > place to keep repositories synced between two servers, one bein the
> > master and one being the standby. I can switch roles between servers
> > as well. From my first read of what info their is about svnsync, it
> > sounds like the destination repository is only ever meant to be
> > read-only. Is that a hard and fast rule? Is there something I could
> > do to switch the roles of destination and source repositories?
> It's not a hard and fast rule, but to switch which repos is the master
> and which is the slave you'd have to manually go in and mess with the
> svnsync revprops on r0 of whichever is the slave. It's definately a
> hard and fast rule that you can only have one master at any given
> time. If you write to both the slave and the master then there's no
> mechanism for resolving the inconsistency.
> > A HOWTO for new features like this will help a lot. I'm willing to
> > write it with some help from the devs that put this feature together.
> Paul Querna put up a HOWTO for basic read-only mirroring on his blog yesterday:
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Sep 14 21:37:03 2006