Mine finished ok. I wish there was some way to eliminate the empty revisions, but this is good enough. - Jorge
On Mon, Sep 14, 2009 at 3:04 PM, GTM <[email protected]> wrote: > > Local sync completed, unfortunately I've gotten much the same result > with the sync stopping at revision 1285. > -Garrett > > On Sep 11, 7:02 pm, Garrett McGrath <[email protected]> wrote: > > I plan too monday morning as im no longer in the office this evening. > Ill post the results once I do that. > > -Garrett > > > > -----Original Message----- > > From: Ben Collins-Sussman <[email protected]> > > Sent: Friday, September 11, 2009 6:25 PM > > To: [email protected] > > Subject: Re: svnsync issue > > > > Great. But you still need to try to sync from local to local. > > > > On Fri, Sep 11, 2009 at 4:59 PM, GTM <[email protected]> wrote: > > > > > Sorry, I wasn't shooting for vague, the project is called MVPA (Multi > > > Voxel Pattern Analysis). And is currently hosted publicly from: > > >https://www.csbmb.princeton.edu/repos/distpat/trunk/mvpa/(and<https://www.csbmb.princeton.edu/repos/distpat/trunk/mvpa/%28and>i > > > stand > > > corrected, our current revision is only 3172) > > > > > The target project I was trying to sync to was: > http://code.google.com/p/princeton-mvpa-test/ > > > > > The repository hosting is currently using svn version v1.4.0 and > > > failed entirely when I attempted to do an svnsync of a portion of the > > > source tree, as that isn't supported on that version of subversion at > > > all. As such, I've done a dump and loaded it onto my desktop which is > > > running v1.6.5, and attempted to do a sync from there using the > > > following commands: > > > > > svnsync init --username (me) > https://princeton-mvpa-test.googlecode.com/svn/ > > > file:///d:/Workingarea/distpat/trunk/mvpa > > > Copied properties for revision 0. > > > svnsync sync --username (me) > https://princeton-mvpa-test.googlecode.com/svn/ > > > Committed revision 1. > > > Copied properties for revision 1. > > > ... > > > Committed revision 1285. > > > Copied properties for revision 1285. > > > > > I just finished a full sync attempt with no luck. > > > -Garrett > > > > > On Sep 11, 4:46 pm, Ben Collins-Sussman <[email protected]> wrote: > > >> On Fri, Sep 11, 2009 at 3:27 PM, GTM <[email protected]> wrote: > > > > >> > I'm attempting to move a project out of a locally hosted SVN into a > > >> > google code SVN and having some difficulty. > > > > >> > I've used svnsync and actually had it run, it runs all the way thru > to > > >> > revision 1200 or so, then it stops as if it's finished the sync (ie, > > >> > there are no errors produced at the end of the sync, it simply > ends). > > >> > However the repository goes well beyond that to around revision > 6300. > > >> > Running the sync command again does not push it to continue syncing. > > > > >> > It should be noted that I am not syncing the entire original > > >> > repository, but instead a sub branch that includes just the code I > > >> > would like to have hosted here as the repository includes a number > of > > >> > peoples other work. I've attempted to simply do an svn dump, then > > >> > filter the dump with svndumpfilter. However due to the constraints > of > > >> > the dumpfilter code that has proven impossible (we have a large > number > > >> > of svn cp commands sourcing locations outside what I am allowing > into > > >> > the filter). > > > > >> > Are there any solutions to the problem? > > > > >> The problem is sufficiently vague in that I don't think anyone can > > >> give you any answers without looking at your specific 'source' > > >> dumpfile or source repository. It would also help if you told us the > > >> name of the project. :-) > > > > >> However, my hunch is that this has little to do with the google code > > >> server, and everything to do with the fragility of history filtered by > > >> svndumpfilter. Here's what I would do: > > > > >> 1. Create a new empty repository on local disk, and try svnsyncing > > >> your source repository into it. Does it complete all the way through? > > > > >> 2. Make your source repository available to the public so others can > > >> download it for examination. > > > > >> 3. Send this post to [email protected], which is an > > >> extremely active users-supporting-users list. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
