From: Junio C Hamano <gitster@pobox.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: git mailing list <git@vger.kernel.org>, srp@srparish.net
Subject: Re: git-daemon breakage in 1.5.4
Date: Tue, 05 Feb 2008 12:02:36 -0800 [thread overview]
Message-ID: <7vr6fr9noj.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: BE051395-F4E1-428B-89B3-5D01BEA42C71@wincent.com
Wincent Colaiuta <win@wincent.com> writes:
> I just noticed that my copy of git-daemon running from xinetd on Red
> Hat Enterprise Linux 3 has been broken since upgrading to 1.5.4.
>
> On the client side this is what you see ("git clone" used in the
> example but you get the same issue with "git ls-remote"):
>
> git clone git://git.wincent.com/wikitext.git
> Initialized empty Git repository in /tmp/wikitext/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.wincent.com/wikitext.git' failed.
>
> Nothing printed to the logs on the server side: it simply hangs up. By
> connecting via telnet I've confirmed that git-daemon is running and
> does accept the initial connection.
>
> The verdict according to "git bisect" is that
> 511707d42b3b3e57d9623493092590546ffeae80 is first bad commit:
>
> commit 511707d42b3b3e57d9623493092590546ffeae80
> Author: Scott R Parish <srp@srparish.net>
> Date: Sun Oct 28 04:17:20 2007 -0700
>
> use only the $PATH for exec'ing git commands
Perhaps you did not install git on the PATH processes launched
by your inetd implementation would use?
next prev parent reply other threads:[~2008-02-05 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 15:39 git-daemon breakage in 1.5.4 Wincent Colaiuta
2008-02-05 17:49 ` Scott Parish
2008-02-05 19:28 ` Wincent Colaiuta
2008-02-05 20:02 ` Junio C Hamano [this message]
2008-02-06 8:05 ` Wincent Colaiuta
2008-02-06 8:46 ` Junio C Hamano
2008-02-06 9:44 ` Wincent Colaiuta
2008-02-06 9:40 ` Johannes Sixt
2008-02-06 10:12 ` Wincent Colaiuta
2008-02-06 10:28 ` Johannes Sixt
2008-02-06 11:39 ` Wincent Colaiuta
2008-02-06 11:33 ` Johannes Sixt
2008-02-06 12:02 ` Adam Piatyszek
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=7vr6fr9noj.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=srp@srparish.net \
--cc=win@wincent.com \
/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.