RE: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request

[Page, Bill]

Ben,

I have been trying to understand why svnsync failed to
mirror the Axiom SourceForge repository and what we can do
about this situation.

First: I was successful at running an svnsync from a
local svn repository (obtained via rsync from SourceForge)
to another newly created local repository. The resulting
mirror had the very desirable property of being the same
size as the original - something that is not true when
using 'svk smerge'.

But I was not successful running svnsync directly from the
repository at SourceForge, presumably because SourceForge is
not yet running SVN 1.4 (among other possible problems at that
site). None the less, it seems that by using rsync to move the
repository files themselves to our axiom-developer.org server
and then access the files as a local repository using the new
version 1.4 of SVN, it is possible to get around this limitation.

However, when I tried to run this same process with the Google
Code repository as the target, I got the error message shown
below.

I can think of three possible explanations:

1) perhaps the pre_properties hook is not set up properly in
   our svn repository at Google?

2) perhaps this is another limitation of using svnsync with
   older versions of svn? (You said earlier that Google also
   was not yet running SVN 1.4)

3) or perhaps this is some system configuration problem such
   as a limitation on the size of the /tmp directory on the
   Google Code server?

What do you recommend? Do you think we should wait until Google
has had a chance to upgrade to SVN 1.4 and then try again?

Or should I give up on moving the whole repository and just
skim-off the most recent revision of trunk, copy trunk to our
branches/build-improvements, and then update it by skimming
off the top revision of that branch? I think that would be the
absolute minimum repository contents what would be useful for
us to maintain on the Google site. At least it would provide
our developers with a presumably more reliable alternative than
the existing SourceForge svn repository. Unfortunately I don't
think it would allow us to move our development process to the
Google environment. :-(

Regards,
Bill Page.

> -----Original Message-----
> From: Page, Bill [mailto:address@hidden 
> Sent: Monday, October 02, 2006 5:11 PM
> To: Ben Collins-Sussman
> Cc: axiom-dev; Gabriel Dos Reis; Bill Page
> Subject: RE: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request
> 
> Ben,
> 
> I response to:
> 
> $ svnsync init https://axiom.googlecode.com/svn
> file:///home/page/axiom-sf
> $ svnsync --non-interactive sync https://axiom.googlecode.com/svn 
> 
> After about an hour of processing I obtained the message:
> 
>   svnsync: At least one property change failed; repository is 
> unchanged
>   Committed revision 1.
>   Copied properties for revision 1.
>   Committed revision 2.
>   Copied properties for revision 2.
> 
> and svnsync stopped.
> 
> Do you have any idea what might have gone wrong?
> 
> Regards,
> Bill Page.
> 
> 
> > -----Original Message-----
> > From: Ben Collins-Sussman [mailto:address@hidden 
> > Sent: Monday, October 02, 2006 10:47 AM
> > To: Bill Page
> > Cc: axiom-dev; Gabriel Dos Reis
> > Subject: Re: [Axiom-developer] RE: [M#73697383] Re: 
> Disk-quota Request
> > 
> > On 10/1/06, Bill Page <address@hidden> wrote:
> > 
> > > Now, how do I use this at Google Code?
> > >
> > 
> > svnsync can replicate any repository to any other, over any network
> > protocol.  So you'd do something like:
> > 
> > # reset google repos to r0
> > # initialize google repos:
> > $ svnsync init https://axiom.googlecode.com/svn 
> > file:///the/original/svn/repos
> > # push the local repos history up to the remote repos
> > $ svnsync --non-interactive sync https://axiom.googlecode.com/svn
> > 
> > Note:  you can use svnsync to 'push' commits at googlecode, 
> but at the
> > moment you can't use it to 'pull' commits down from googlecode,
> > because we've not yet upgraded googlecode to svn 1.4.  (Though we're
> > actively working on it.)  But the method above is a way of at least
> > initially populating your googlecode repository.
> > 
> > Btw, I've just reset your repository back to revision 0.
> > 
>