From: Deskin Miller <deskinm@umich.edu>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn clone problem
Date: Wed, 27 May 2009 19:11:01 -0700 [thread overview]
Message-ID: <86d4c5e00905271911g58cccc1bwd4b881541db6f7a5@mail.gmail.com> (raw)
In-Reply-To: <20090527221601.GA12914@mail.oracle.com>
On Wed, May 27, 2009 at 15:16, Joel Becker <Joel.Becker@oracle.com> wrote:
> Hello everyone,
> I've got a fun git-svn bug I can't seem to track down. The
> google is no help. I'm just trying to clone a full repo. I'm not
> looking to push changes back, and I've done this before, yet now (1.6.3
> and 1.6.3.1) it's not working.
> The clone command and error is:
>
> $ git svn clone --stdlayout --no-metadata -Aauthors http://oss.oracle.com/projects/oracleasm/src/ driver-git
> Initialized empty Git repository in
> /build/jlbec/oracleasm/driver-git/.git/
> A kernel/osm.c
> A Configure
> A include/osmprivate.h
> A include/arch-i386/osmstructures.h
> A include/osmlib.h
> A include/osmerror.h
> A libosm/osmlib.c
> A Makefile
> r1 = d855bc271ef7dcf70a58ae35fde5dc49f28d3e8e (trunk)
> missing UUID at the end of .git/svn/trunk/.rev_db.????????-????-????-????-???????????? at /usr/lib/git-core/git-svn line 4488
>
> You can drop the --no-metadata if you like - it doesn't help. Clearly
> it's tripping on the first revision. I'm not sure what UUID it's
> looking for. The manpage speaks of UUIDs in regards to svk/svnsync, and
> I'm not using those.
> I suspect the last time I did this was in the 1.5 range (my
> distribution has obviously moved on). But I would think this was tested
> :-)
>
> Joel
>
> --
>
> "Behind every successful man there's a lot of unsuccessful years."
> - Bob Brown
>
> Joel Becker
> Principal Software Developer
> Oracle
> E-mail: joel.becker@oracle.com
> Phone: (650) 506-8127
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:
<lp3:repository-uuid>
612f8ebc-c883-4be0-9ee0-a4e9ef946e3a
</lp3:repository-uuid>
However when I do the same with oss.oracle.com I see
<lp2:repository-uuid>
????????-????-????-????-????????????
</lp2:repository-uuid>
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.
Deskin Miller
next prev parent reply other threads:[~2009-05-28 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 22:16 git-svn clone problem Joel Becker
2009-05-28 2:11 ` Deskin Miller [this message]
2009-05-28 2:41 ` Joel Becker
2009-05-28 7:47 ` Matthias Andree
2009-05-28 17:22 ` Joel Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86d4c5e00905271911g58cccc1bwd4b881541db6f7a5@mail.gmail.com \
--to=deskinm@umich.edu \
--cc=Joel.Becker@oracle.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).