From: Anand Kumria <wildfire@progsoc.org>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [bug] git svn clone failing with invalid diff stream
Date: Wed, 21 Apr 2010 02:42:25 +1000 [thread overview]
Message-ID: <j2x971f65791004200942yf86f51b2mc828dbd19c169b28@mail.gmail.com> (raw)
In-Reply-To: <4BCDD25F.4030406@drmicha.warpmail.net>
On Wed, Apr 21, 2010 at 2:12 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> 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.
Thanks - I was afraid I was doing something incorrect or it might have
been some other issue at my end.
I've reached out to the Berlios and Subversion guys, since the page on
fsfsverify seems to indicate it is a hard to reproduce problem needing
a test case; and this appears to be one.
Cheers,
Anand
prev parent reply other threads:[~2010-04-20 16:42 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
2010-04-20 16:42 ` Anand Kumria [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=j2x971f65791004200942yf86f51b2mc828dbd19c169b28@mail.gmail.com \
--to=wildfire@progsoc.org \
--cc=git@drmicha.warpmail.net \
--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).