From: Joel Becker <Joel.Becker@oracle.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-svn clone problem
Date: Wed, 27 May 2009 15:16:01 -0700 [thread overview]
Message-ID: <20090527221601.GA12914@mail.oracle.com> (raw)
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
next reply other threads:[~2009-05-27 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 22:16 Joel Becker [this message]
2009-05-28 2:11 ` git-svn clone problem Deskin Miller
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=20090527221601.GA12914@mail.oracle.com \
--to=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).