git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [bug] git svn clone failing with invalid diff stream

From
AKAnand Kumria <wildfire@progsoc.org>
Date
Apr 20, 2010, 16:42 UTC
Message-ID
<j2x971f65791004200942yf86f51b2mc828dbd19c169b28@mail.gmail.com>
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:

Show 28 quoted lines
> 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

Previous: Michael J Gruber
Message 3 of 3 in “[bug] git svn clone failing with invalid diff stream”
  1. Anand KumriaApr 20, 2010
  2. Michael J GruberApr 20, 2010
  3. Anand KumriaApr 20, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.