From: Markus Heidelberg <markus.heidelberg@web.de>
To: Lachlan Deck <lachlan.deck@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn clone failure
Date: Sat, 28 Mar 2009 16:20:29 +0100 [thread overview]
Message-ID: <200903281620.29564.markus.heidelberg@web.de> (raw)
In-Reply-To: <F76E6356-60EB-4FDE-B97E-CB34FF2D7017@gmail.com>
Lachlan Deck, 28.03.2009:
> On 28/03/2009, at 11:59 PM, Markus Heidelberg wrote:
>
> > Lachlan Deck, 27.03.2009:
> >> Hi there,
> >>
> >> I'm trying to clone an existing svn repository with git (just getting
> >> started with git) and it keeps failing with:
> >> ...
> >> r604 = 6428e63734a21ee5fcb4593274747e2758578a91 (git-svn)
> >> fatal: unable to run 'git-svn'
> >
> > Are you sure r604 isn't the latest svn revision?
>
> A few thousand out, yes.
>
> > I always get this error when doing "git svn fetch" with an http URL,
> > it
> > doesn't occur with an svn URL. But everything seems to work fine,
> > though.
>
> Interesting. Yes, it's from an https url. I'll try svn+ssh://..
> But are you saying there's no way to get more info about the error?
At least I don't have more info about it except for this:
I use Gentoo Linux and the git ebuild (I have the distribution package
installed, but use the self-compiled git) says
"Per Gentoo bugs #223747, #238586, when subversion is built"
"with USE=dso, there may be weird crashes in git-svn. You"
"have been warned."
I have subversion compiled with dso (Enable runtime module search), it's
enabled per default. And since it worked, I didn't change it. But it
would be interesting to see, if this error has something to do with it.
Maybe I'll try it out.
Markus
next prev parent reply other threads:[~2009-03-28 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 21:18 git svn clone failure Lachlan Deck
2009-03-28 12:59 ` Markus Heidelberg
2009-03-28 14:16 ` Lachlan Deck
2009-03-28 15:20 ` Markus Heidelberg [this message]
2009-03-28 17:29 ` Lachlan Deck
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 22:28 Gabor Gombas
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=200903281620.29564.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=git@vger.kernel.org \
--cc=lachlan.deck@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.