On Tue, Sep 16, 2008 at 8:43 PM, Gilles <[EMAIL PROTECTED]> wrote: > > Hi, > I recently created a google code project. My project has been hosted > on a subversion server so far, but I dont have access to other than > through https. I wanted to import the project's existing history into > the google code svn. THis is what I did: > I read the FAQ stating that I have to use svnsync. But svnsync > requires access to the SVN repository (which I dont). So, I had to ask > one of the administrators to create a dump of my project's SVN history > (using svnadmin dump > project.dump). I then created my own repository > from the dump file: > svnadmin create my_repo > svnadmin --force-uuid load my_repo < project.dump
Yikes, this was complete overkill. The entire point of svnsync is that you *don't* need direct access to *either* the source or destination repositories. svnsync just 'checks out' each revision from the source repository and 'commits' to the destination repository. As long as you can 'svn checkout' from the source, and 'svn commit' to the destination, you're all set. Sorry you went through all this unecessary work of dumping and reloading! > > From there, I checked out a copy of my project (svn co > file:///path/to/my_repo), > and svn info reports the same UUID as other existing working copies > still pointing to the previous svn server (not the google code one). > I sync'ed the google code svn with the local repo using the > instructions in the FAQ (svnsync init and svnsync sync). > > Everything went fine, except that when I wanted to switch my working > copies to the google code svn, this is what I ended up with: > svn switch --relocate https://myold_repo/ https://v4l4j.googlecode.com/svn > svn: The repository at 'https://v4l4j.googlecode.com/svn' has uuid > 'f47d2976-8228-11dd-9899-c7ba65f7c4c7', but the WC has '3029d069- > df0c-0410-bf5d-8c55c6c14d23' > Weird considering that: > - I used --force-uuid when creating my local repository > - the check out from my local repository shows the same uuid as other > working copies (checked out from the previous svn server) > > Why isnt the correct uuid picked up by the google code svn server when > sync'ing ? Because your target (googlecode) repository has its own unique UUID; it was created when the repository itself was created. svnsync doesn't have the power to change repository UUIDs. Remember, it just 'pulls' via checkout and 'pushes' via commit, like any normal svn client. > What did I do wrong ? I can provide the dump file used to create my > local repository if need. You didn't do anything wrong... you created a 2nd repository that mirrors the old one, but it's not the same repository. It has a unique UUID. 'svn switch --relocate' rewrites the urls stashed in your working copy metadata, but only if it's still the same repository. Two possible actions: - try adding --force to your relocate command - just do fresh checkouts (it only took me 10 seconds to check out your /trunk!) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
