From: Michael J Gruber <git@drmicha.warpmail.net>
To: Anand Kumria <wildfire@progsoc.org>
Cc: git@vger.kernel.org
Subject: Re: [bug] git svn clone failing with invalid diff stream
Date: Tue, 20 Apr 2010 18:12:15 +0200 [thread overview]
Message-ID: <4BCDD25F.4030406@drmicha.warpmail.net> (raw)
In-Reply-To: <m2q971f65791004192348zab4adf13p93a6a4c1d60f9c16@mail.gmail.com>
Anand Kumria venit, vidit, dixit 20.04.2010 08:48:
> Hi,
>
> Using both git 1.7.0.4 and 1.5.6.5 I am unable to clone the Subversion
> respository for Serendipity.
>
> URL: svn://svn.berlios.de/serendipity
>
> It fails consistently on r1341 with:
>
> (1.5.6.5): Svndiff data contains invalid instruction: Invalid diff
> stream: [tgt] insn 335 starts beyond the target view position at
> /usr/bin/git-svn line 3856
>
> and
>
> (1.7.0.4): Svndiff data contains invalid instruction: Invalid diff
> stream: [tgt] insn 335 starts beyond the target view position at
> /usr/lib/git-core/git-svn line 5047
>
> On, seemingly UTF-8 encoded data. Any ideas / pointers would be appreciated.
That message actually comes from the underlying svn diff itself. To me
it looks like a problem with the underlying fsfs on the server:
http://www.szakmeister.net/fsfsverify/
hg convert runs into the same problem, btw.
It would be worthwhile to try svnsync and clone the synced repo, but it
seems berlios does not support the necessary replay command. Time to
talk to them!
Michael
next prev parent reply other threads:[~2010-04-20 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 6:48 [bug] git svn clone failing with invalid diff stream Anand Kumria
2010-04-20 16:12 ` Michael J Gruber [this message]
2010-04-20 16:42 ` Anand Kumria
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=4BCDD25F.4030406@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=wildfire@progsoc.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 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.