Ben, Could you please arrange to reset the Axiom repository at Google Code back to "empty" and incorporate the "pre-revprop-change" hook as required by 'svnsync'? Later today I can try to use 'svnsync' as in my test below to re-populate our repository at Google.
The documentation of 'svnsync' refers to the mirror that it constructs as "read-only". I presume that this means only that there is no provision for two-way updating of the mirror via this mechanism? So we would be free to commit changes at Google but we might have to use some other method (e.g. svk smerge') to maintain more than one copy of this archive. Right? Thanks. Bill Page. > -----Original Message----- > From: Bill Page [mailto:[EMAIL PROTECTED] > Sent: October 1, 2006 2:17 PM > To: 'Ben Collins-Sussman' > Cc: 'axiom-dev'; 'Gabriel Dos Reis'; 'Bill Page' > Subject: RE: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request > > > Earlier I wrote: > > > > > But the 'svnsync sync' command says: > > > > $ svnsync --non-interactive sync file:///home/page/axiom_sync > > > > svnsync: REPORT request failed on > > 'https://svn.sourceforge.net/svnroot/axiom' > > svnsync: The requested report is unknown. > > ... > > Ok, the following worked, starting with a local backup copy of the > repository that was rsync'd from SourceForge. > > $ svnadmin create /home/page/axiom_sync2 > $ echo '#!/bin/sh' > /home/page/axiom_sync2/hooks/pre-revprop-change > $ chmod 755 /home/page/axiom_sync2/hooks/pre-revprop-change > $ svnsync init file:///home/page/axiom_sync2 file:///home/page/test0 > $ svnsync --non-interactive sync file:///home/page/axiom_sync2 > ... > Committed revision 165. > Copied properties for revision 165. > $ du -s axiom_sync2 > 156792 axiom_sync2 > > ------- > > And it's the same size. Great! > > Now, how do I use this at Google Code? > > Regards, > Bill Page. > > > _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
