From: Thomas Rast <trast@student.ethz.ch>
To: Sebastian Pipping <webmaster@hartwork.org>
Cc: "Nicolas Sebrecht" <nicolas.s.dev@gmx.fr>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
git@vger.kernel.org
Subject: Re: [BUG?] Re: fail to svn clone debian's kernel repository
Date: Wed, 3 Mar 2010 15:33:12 +0100 [thread overview]
Message-ID: <201003031533.13056.trast@student.ethz.ch> (raw)
In-Reply-To: <4B8DB940.9020609@hartwork.org>
On Wednesday 03 March 2010 02:20:00 Sebastian Pipping wrote:
> git svn init file://"${ABS_SVN_SOURCE}" \
> --trunk=trunk --tags=NOTAGS --branches=NOBRANCHES
> git svn fetch -r1:1890
> git config --remove-section 'svn-remote.svn'
> git svn init file://"${ABS_SVN_SOURCE}" \
> --trunk=main/trunk --tags=main/tags --branches=main/branches
> git svn fetch -r1891:HEAD
[...]
> Invalid filesystem path syntax: Cannot replace a directory from within
> at /usr/libexec/git-core/git-svn line 5089
While arguably[*] a bug, you can work around it by simply not removing
the previous trunk from git-svn's 'fetch' lines. I.e., the following
config works for me after r1890:
[svn-remote "svn"]
url = file:///.../portage-anon-svn-repo-dump
fetch = main/trunk:refs/remotes/trunk2
branches = main/branches/*:refs/remotes/branches/*
tags = main/tags/*:refs/remotes/tags/*
fetch = trunk:refs/remotes/trunk
You can later use update-ref (or even just mv) to rename trunk2 to
trunk.
You may also want to place the cutoff in the above commands at
1889/1890 instead, since r1890 is the one that does the move.
Combining this fix with the above config results in correct
"continuous" history of trunk, whereas merely using the config above
results in a disconnect at the move.
[*] SVN also fails if you check out trunk@1889 and attempt to 'svn update' it
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-03-03 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:05 [BUG?] fail to svn clone debian's kernel repository Uwe Kleine-König
2009-06-10 18:42 ` Uwe Kleine-König
2010-03-01 2:08 ` Sebastian Pipping
2010-03-02 19:54 ` [BUG?] " Nicolas Sebrecht
2010-03-03 1:20 ` Sebastian Pipping
2010-03-03 14:33 ` Thomas Rast [this message]
2010-03-04 2:03 ` Sebastian Pipping
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=201003031533.13056.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
--cc=u.kleine-koenig@pengutronix.de \
--cc=webmaster@hartwork.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).