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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <hanwen@xxxxxxxxx> 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 - hanwen@xxxxxxxxx - http://www.xs4all.nl/~hanwen

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]