From: Matthias Andree Date: Thu, 28 May 2009 07:47:16 GMT Subject: Re: git-svn clone problem Message-ID: In-Reply-To: <20090528024153.GH12914@mail.oracle.com> Am 28.05.2009, 04:41 Uhr, schrieb Joel Becker : > On Wed, May 27, 2009 at 07:11:01PM -0700, Deskin Miller wrote: >> The problem here isn't with git-svn; rather, it is with the svn >> repository at oss.oracle.com claiming a nonsensical UUID. svn uses >> UUIDs behind the scenes to identify each repository, and git-svn does >> the same thing. When doing git svn init (or clone, which is just init >> && fetch) the svn server sends back a UUID which identifies it. When >> I use wireshark and expand the first HTTP packet back from a good svn >> server, I see something like the following embedded in the xml tree: >> >> >> 612f8ebc-c883-4be0-9ee0-a4e9ef946e3a >> >> >> However when I do the same with oss.oracle.com I see >> >> >> ????????-????-????-????-???????????? >> >> >> git-svn tries to play along for a while, but the bottom line is that a >> string of question marks isn't a UUID. >> >> There's more about svn's use of UUIDs in the svn book. Perhaps the >> admin of oss.oracle.com can correct this UUID problem so one can use >> git-svn with this repository. > > Is this some new feature of svn that git-svn has decided to > require? We're running subversion 1.4.4 there, and git-svn used to work > against those repos. > Hmm, it's only a couple of very old repos with this problem - > they were probably created with subversion 1.1 or 1.0. I found how to > fix it. Thanks. Hi Joel, could you share a pointer to or outline of the solution with the list, for the completeness of the (searchable) archives? Thanks. -- Matthias Andree