From: Michael Olson <mwolson@member.fsf.org>
To: Blair Zajac <Blair@orcaware.com>
Cc: git@vger.kernel.org
Subject: Re: git svn clone of subversion's own code failing
Date: Wed, 21 Apr 2010 14:18:46 -0700 [thread overview]
Message-ID: <i2qc8b3bef91004211418x1496785dqce43607ad1a49e65@mail.gmail.com> (raw)
In-Reply-To: <B3F7BC3A-9606-48BF-A0C8-093CA42B3720@orcaware.com>
On Wed, Apr 21, 2010 at 11:55 AM, Blair Zajac <Blair@orcaware.com> wrote:
> Using MacPorts with git 1.7.0.4 and Subversion 1.6.11, ironically, cloning Subversion's own source code is failing. I'm using a larger log window size to make the scan to svn's first commit in the repository much faster:
>
> $ git svn clone --log-window-size 5000 -s https://svn.apache.org/repos/asf/subversion
>
> It ends up failing with:
>
> r855619 = c93a05b8f94c53b8748ffe9352445209fe648e87 (refs/remotes/trunk)
> M contrib/client-side/svn-clean
> r855620 = a6b138d3112b1ea0b51b112c6598aae5644369ae (refs/remotes/trunk)
> M subversion/bindings/swig/core.i
> M subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c
> A subversion/bindings/swig/python/libsvn_swig_py/svn_old_swig.h
> M subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.h
> M subversion/bindings/swig/include/svn_global.swg
> M subversion/bindings/swig/include/svn_types.swg
> r855621 = 41bbc61c035218937f1032381f02c481c8653a22 (refs/remotes/python-bindings-improvements)
> W:svn cherry-pick ignored (subversion/trunk:855604) - missing 79 commit(s) (eg 462871a2ededa70304eeb99affe550fd029557b5)
> r855622 = 2c62a0cca702ffe59dabee92220cf28aedfe1c84 (refs/remotes/python-bindings-improvements)
> fatal: ambiguous argument '3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions
> rev-list 3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b: command returned error: 128
I ran into the same issue. A temporary hack can be found in the
thread "[PATCH/RFC 2/2] git-svn: Don't allow missing commit parent to
stop git-svn", but it is probably not a real solution to the problem.
--
Michael Olson | http://mwolson.org/
prev parent reply other threads:[~2010-04-21 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 18:55 git svn clone of subversion's own code failing Blair Zajac
2010-04-21 21:18 ` Michael Olson [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=i2qc8b3bef91004211418x1496785dqce43607ad1a49e65@mail.gmail.com \
--to=mwolson@member.fsf.org \
--cc=Blair@orcaware.com \
--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).