From: Junio C Hamano <junkio@cox.net>
Date: Tue, 23 Jan 2007 00:44:02 GMT
Subject: Re: Meaning of "fatal: protocol error: bad line length character"?
Message-ID: <7v3b62r2r1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <45B5535E.2000808@xs4all.nl>

Han-Wen Nienhuys <hanwen@xs4all.nl> 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.