git svn: Bad URL passed to RA layer: Unrecognized URL scheme

I made an ill-advised upgrade to from subversion-1.4.6 to
subversion-1.5.2. While I had subversion-1.5.2 installed, git svn rebase
ended with a 'segmentation fault' error. 

Now back at subversion-1.4.6, git repositories with svn remotes updated
during the aforentioned upgrade now give an error:

(master) $ git svn fetch
Bad URL passed to RA layer: Unrecognized URL scheme for 'http://code.djangoproject.com/svn' at /usr/libexec/git-core/git-svn line 1400

(master) $ git svn rebase
Bad URL passed to RA layer: Unrecognized URL scheme for 'http://code.djangoproject.com/svn' at /usr/libexec/git-core/git-svn line 1909

Others which were not updated recently work fine for git svn operations.

How can I repair the affected git repositories?

Thanks.

2008/10/5 Jeff Kowalczyk [off-list ref]:

I made an ill-advised upgrade to from subversion-1.4.6 to
subversion-1.5.2. While I had subversion-1.5.2 installed, git svn rebase
ended with a 'segmentation fault' error.

Now back at subversion-1.4.6, git repositories with svn remotes updated
during the aforentioned upgrade now give an error:

(master) $ git svn fetch
Bad URL passed to RA layer: Unrecognized URL scheme for 'http://code.djangoproject.com/svn' at /usr/libexec/git-core/git-svn line 1400

(master) $ git svn rebase
Bad URL passed to RA layer: Unrecognized URL scheme for 'http://code.djangoproject.com/svn' at /usr/libexec/git-core/git-svn line 1909

Others which were not updated recently work fine for git svn operations.

How can I repair the affected git repositories?

Thanks.

That somehow looks more like an svn error than a git error, does
svn checkout http://code.djangoproject.com/svn
work?

-- 
Mikael Magnusson

Mikael Magnusson wrote:

That somehow looks more like an svn error than a git error, does
svn checkout http://code.djangoproject.com/svn work?

You were correct, I tried subversion and got the same error. I rebuilt
(gentoo ~x86) neon-0.28.3, subversion-1.5.2 and git-1.6.0.2, and have
functional git svn operations.

However, each operation ends with a segmentation fault. This is the case
with all git svn repositories (e.g. several different svn remote hosts).

  (master) $ git svn rebase
     M  django/core/management/commands/makemessages.py
     M  docs/topics/i18n.txt
  r9155 = 4c86e60f62366ac9c3fd9369c17c54801a8f2ea0 (trunk)
  First, rewinding head to replay your work on top of it...
  Fast-forwarded master to refs/remotes/trunk.
  Segmentation fault

Does the segfault risk corruption of the git repository data?

Would I report this as a git bug or distribution bug?

Thanks.

Jeff Kowalczyk wrote:

However, each operation ends with a segmentation fault. This is the case
with all git svn repositories (e.g. several different svn remote hosts).

  (master) $ git svn rebase
     M  django/core/management/commands/makemessages.py
     M  docs/topics/i18n.txt
  r9155 = 4c86e60f62366ac9c3fd9369c17c54801a8f2ea0 (trunk)
  First, rewinding head to replay your work on top of it...
  Fast-forwarded master to refs/remotes/trunk.
  Segmentation fault

Can you try to find out what exactly segfaults here? git-svn is
implemented in Perl, so that means it's either Perl itself (unlikely),
the SVN libraries hooked into Perl, or some git command run by
git-svn.

- Thomas

-- 
Thomas Rast
trast@{inf,student}.ethz.ch