From: Derek Fawcus <dfawcus@cisco.com>
To: git@vger.kernel.org
Subject: git-svn - failed to clone repository
Date: Wed, 23 Jul 2008 17:06:59 +0100 [thread overview]
Message-ID: <20080723160659.GB6705@cisco.com> (raw)
I tried to create a clone of an svn repository, and it gave
up part way through with the following error:
Incomplete data: Delta source ended unexpectedly at /usr/bin/git-svn line 3858
Looking at the source, this is the call '$reporter->finish-report($pool)'
near the end of gs_do_update.
This is using git 1.5.6 from the etch backports repository.
The repository in question was cocotron, the command being:
git svn clone http://cocotron.googlecode.com/svn -t tags -b branches -T trunk
It seemed to fail at revision 91, the last couple of lines of the command output being:
r90 = <hex I can't be bothered to type unless required> (trunk)
M Foundation/NSStream/NSFileHandle.m
then followed by the above error. Looking at the actual revision
page (http://code.google.com/p/cocotron/source/detail?r=91)
the only thing that stands out as odd is one file claims to be 'too large to diff'.
It's ~900k and if one grabs and diffs by hand, the output is only ~70 lines.
So - is this at all related to the 'known bug' mentioned earlier - stopped on
line 3856 when using line ending mapping (I'm not using such), or is this
something else?
Last, assuming I was to simply grab and apply this changeset by hand,
what would I need to do to fix up metadata so that git-svn could continue
importing the history? There are about 200 changesets in the whole repository.
Thanks,
DF
next reply other threads:[~2008-07-23 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:06 Derek Fawcus [this message]
2008-07-23 17:08 ` git-svn - failed to clone repository SZEDER Gábor
2008-07-23 19:49 ` Avery Pennarun
2008-07-23 22:59 ` Derek Fawcus
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=20080723160659.GB6705@cisco.com \
--to=dfawcus@cisco.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).