Subject: Re: Meaning of "fatal: protocol error: bad line length character"?

From: Han-Wen Nienhuys <[email-masked]>
Date: Tue, 23 Jan 2007 01:53:35 +0100

Sylvain, can you help out here? 

The lilypond repo got into a state where it will no longer
allow reading over the git:// protocol; for troubleshooting,
we need some info on what is happening on the GNU side of things.

Han-Wen

Junio C Hamano escreveu:
> Han-Wen Nienhuys <[email-masked]> writes:
> 
>> if you need another example where this is happening, the anongit
>> repo for lilypond seems to have gotten in this state as well,
>>
>> [hanwen@haring tmp]$ git clone git://git.sv.gnu.org/lilypond.git
>> Initialized empty Git repository in /tmp/lilypond/.git/
>> fatal: protocol error: bad line length character
>> fetch-pack from 'git://git.sv.gnu.org/lilypond.git' failed.
> 
> With my debugging patch applied to peek-remote:
> 
>         $ git-peek-remote git://git.sv.gnu.org/lilypond.git
>         error: protocol error: bad line length character
>         <<<<<
>         env: 
>         >>>>>
>         fatal: protocol error: bad line length character
> 
> So somebody says "env:" immediately followed by an EOF to the
> stdout when upload-pack is invoked via git-daemon.
> 
> The first thing that happens in the fetch/clone/peek-remote
> protocol is reading from the server side, so unfortunately there
> is no way to debug any further without having an access to their
> server.
> 

-- 
 Han-Wen Nienhuys - [email-masked] - http://www.xs4all.nl/~hanwen