Yeah I was just reading this:
"By default, the aforementioned basic requirements of a mirror are that it
> allows revision property modifications and that it contains no version
> history. However, as of Subversion 1.7, you may now optionally disable the
> verification that the target repository is empty using the
> --allow-non-empty option. While the use of this option should not become
> habitual (as it bypasses a valuable safeguard mechanism), it does aid in
> one very common use-case: initializing a copy of a repository as a mirror
> of the original. This is especially handy when setting up new mirrors of
> repositories which contain a large amount of version history. Rather than
> initialize a brand new repository as a mirror and then syncronize all of
> the history into it, administrators will find it *significantly* faster
> to first make a copy of the mature repository (perhaps using *svnadmin
> hotcopy*) and then use *svnsync initialize --allow-non-empty* to
> initialize that copy as a mirror which is now already up-to-date with the
> original."
Now here's the interesting part. I'm running svn 1.6 on the source repo,
1.7 on the mirror repo... (I think)
Geoff Hoffman
Solutions Architect & LAMP Engineer
_____________________________________
Twitter: @m2guru <http://www.twitter.com/m2guru> |
@cardinalpath<http://www.twitter.com/cardinalpath>
LinkedIn: www.linkedin.com/in/geoffreydhoffman
Phone: 480.285.1622 x313
Mobile: 480.231.8323
_____________________________________
www.cardinalpath.com<http://www.cardinalpath.com/?utm_source=signature&utm_medium=CPemail&utm_campaign=dEckman>
training.cardinalpath.com<http://training.cardinalpath.com/?utm_source=signature&utm_medium=CPemail&utm_campaign=dEckman>
*PublicInsite, VKI Studios, and WebShare have merged to form Cardinal Path*
On Fri, Mar 2, 2012 at 8:45 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Fri, Mar 2, 2012 at 10:41 AM, Geoff Hoffman
> <ghoffman_at_cardinalpath.com> wrote:
> > I'm learning some gotchas with svnsync this week. As per my typical
> method
> > of learning I try 3 wrong ways before finally realizing the right way to
> do
> > most things.
> >
> > We have about a 1GB svn repo on Ubuntu at -r 3738, and I'm trying to get
> it
> > mirrored on Win 7 running VisualSVN.
> >
> > I created the mirror repository fine, ran svnsync init and svnsync sync
> on
> > it, then as it started going from -r 1, -r 2, -r 3..., I realized it
> would
> > take a week or more to fetch all nearly 4K commits.
> >
> > So I stopped it, deleted it, started over and did an svnadmin dump -->
> > svnadmin load from the dump -- which ran/imported much faster, but now
> when
> > I try to initialize the sync, I get
> >
> > svnsync: Cannot initialize a repository with content in it
> >
> > D'OH! I forgot to svnsync init after creating the empty mirror repo.
> Whoops.
> >
> > So, my question is, before I whack a perfectly fine "almost mirrored"
> > repository, can I svn propset -r 0 all the stuff needed by svnsync
> manually,
> > to start syncing at -r 3738?
> >
> > Or can I set up the repo again (svnadmin create immediately followed by
> > svnsync init) and then svnadmin load (since load from a dump is so much
> > faster)?
> >
> > It would seem odd that the only way to mirror a repo is to replay
> everything
> > from -r 0.
>
> This is, in fact, a limitation of svnsync. You can manually setup the
> properties on r0 as one option, or if you have svnsync from 1.7
> installed, you can use the new --allow-non-empty option on the init
> command and it essentially will do the same thing for you.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
--
This email, including any attachments, is for the sole use of the intended
recipient and may contain confidential information. If you are not the
intended recipient, please immediately notify us by reply email or by
telephone, delete this email and destroy any copies. Thank you.
Received on 2012-03-02 16:47:42 CET