From: Eric Wong <normalperson@yhbt.net>
To: Tim Janik <timj@imendio.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn breaks on gtk+ import
Date: Mon, 7 Apr 2008 01:20:07 -0700 [thread overview]
Message-ID: <20080407082007.GB28853@soma> (raw)
In-Reply-To: <20080308074737.GC1583@hand.yhbt.net>
Eric Wong <normalperson@yhbt.net> wrote:
> Tim Janik <timj@imendio.com> wrote:
> > hi Eric.
> >
> > with git-svn from git 1.5.4.3, imports of the Gtk+ repository fail:
> >
> > git-svn clone -T trunk -b branches -t tags -r 19001
> > http://svn.gnome.org/svn/gtk+
> > Using existing [svn-remote "svn"]
> > Using higher level of URL: http://svn.gnome.org/svn/gtk+ =>
> > http://svn.gnome.org/svn/gtk%2B/http:
> > No such file or directory: PROPFIND request failed on
> > '/svn/gtk%252B/http%3A': Could not open the requested SVN filesystem at
> > /usr/bin/git-svn line 1352
> >
> > trying the same for glib works fine:
> >
> > git-svn clone -T trunk -b branches -t tags -r 6601
> > http://svn.gnome.org/svn/glib
> > [...]
> > r6601 = 987f6388b211281d08fce0e63936d9e612ed4d4f (trunk)
> > Checked out HEAD:
> > http://svn.gnome.org/svn/glib/trunk r6601
> >
> > looks like the '+' in the the http://svn.gnome.org/svn/gtk+ repository
> > name isn't handled correctly.
>
> It's a known bug which I haven't had time to track down and fix.
>
> git-svn handles files and directories with '+' within the base URL
> you're tracking correctly, but somewhere along the way the base URL
> you're tracking doesn't work correctly for HTTP.
>
> As Harvey suggested, use the svn:// repository for now.
Hi Tim, the HTTP repository should be fixed with the patch in
http://article.gmane.org/gmane.comp.version-control.git/78961
--
Eric Wong
prev parent reply other threads:[~2008-04-07 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 18:00 git-svn breaks on gtk+ import Tim Janik
2008-03-07 19:41 ` Harvey Harrison
2008-03-07 20:09 ` Tim Janik
2008-03-07 20:19 ` Tommi Komulainen
2008-03-08 7:47 ` Eric Wong
2008-04-07 8:20 ` Eric Wong [this message]
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=20080407082007.GB28853@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=timj@imendio.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.