All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: Meaning of "fatal: protocol error: bad line length character"?
Date: Mon, 22 Jan 2007 16:44:02 -0800	[thread overview]
Message-ID: <7v3b62r2r1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <45B5535E.2000808@xs4all.nl> (Han-Wen Nienhuys's message of "Tue, 23 Jan 2007 01:14:22 +0100")

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.

  reply	other threads:[~2007-01-23  0:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 12:04 Meaning of "fatal: protocol error: bad line length character"? Bill Lear
2007-01-20 19:24 ` Junio C Hamano
2007-01-20 19:33   ` Junio C Hamano
2007-01-20 19:54     ` Bill Lear
2007-01-20 20:07       ` Jakub Narebski
2007-01-20 20:20       ` Junio C Hamano
2007-01-20 20:42         ` Junio C Hamano
2007-01-20 21:37           ` Shawn O. Pearce
2007-01-22 20:15             ` Junio C Hamano
2007-01-22 18:58           ` Bill Lear
2007-01-22 19:45             ` Junio C Hamano
2007-01-22 19:55               ` Bill Lear
2007-01-22 22:16                 ` Bill Lear
2007-01-22 22:33                   ` Junio C Hamano
2007-01-23  0:14   ` Han-Wen Nienhuys
2007-01-23  0:44     ` Junio C Hamano [this message]
2007-01-23  0:53       ` Han-Wen Nienhuys

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=7v3b62r2r1.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=hanwen@xs4all.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.