git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommi Komulainen <tommi.komulainen@iki.fi>
To: git@vger.kernel.org
Subject: Re: git-svn breaks on gtk+ import
Date: Fri, 07 Mar 2008 22:19:42 +0200	[thread overview]
Message-ID: <fqs80v$98n$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0803071844510.27175@master.birnet.private>

Tim Janik 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

> looks like the '+' in the the http://svn.gnome.org/svn/gtk+ repository
> name isn't handled correctly.

I had somewhat similar problem with git-svn fetch to a repository 
created with 1.5.3.something failing issuing REPORT. I've tracked down 
the problem to commit f5530b8833bcaa423cd53d133d3de3fa0173fbf3 to git, 
reverting it seems to fix git-svn fetch for me. YMMV.

I tried to follow where/how URL escaping happens / isn't happening 
(there are issues like 'if (<unescaped url> eq <escaped url>)' around - 
mostly because repos_root is escaped) but couldn't get things working. :-/


-- 
Tommi Komulainen                                 tommi.komulainen@iki.fi


  parent reply	other threads:[~2008-03-07 20:25 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 [this message]
2008-03-08  7:47 ` Eric Wong
2008-04-07  8:20   ` Eric Wong

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='fqs80v$98n$1@ger.gmane.org' \
    --to=tommi.komulainen@iki.fi \
    --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).