From: Jeff Garzik <jeff@garzik.org>
To: Todd Zullinger <tmz@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [bug] git cannot find "git pull"?
Date: Sat, 13 Jun 2009 13:22:49 -0400 [thread overview]
Message-ID: <4A33E069.4050401@garzik.org> (raw)
In-Reply-To: <20090613150451.GK5076@inocybe.localdomain>
Todd Zullinger wrote:
> Jeff Garzik wrote:
>> FWIW, to reproduce my Fedora install, this is the setup I always use
>> for my lab computers:
>>
>> * perform a fresh format + install, not an upgrade
>> * uncheck 'office' category
>> * check 'software development' category
>> * do not select 'customize now', thus using Fedora's default package
>> selection
>
> Stranger and stranger. I followed the above steps with an F-11/x86
> network install and then ran:
Found it! A forgotten package I created, a collective of shell scripts,
was setting GIT_EXEC_PATH=/usr/local/bin.
Given that /usr/local/bin/*git* has not existed on my systems for a long
time, it appears that this is a new behavior, being a bit more strict in
complaining about an invalid GIT_EXEC_PATH, rather than simply falling
back to the internal compiled default (/usr/libexec/git-core).
Things are working again now that the local GIT_EXEC_PATH export is removed.
Jeff
next prev parent reply other threads:[~2009-06-13 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 0:10 [bug] git cannot find "git pull"? Jeff Garzik
2009-06-12 1:17 ` Todd Zullinger
2009-06-12 2:44 ` Junio C Hamano
2009-06-12 3:18 ` Todd Zullinger
2009-06-12 5:15 ` Junio C Hamano
2009-06-12 6:52 ` J.H.
2009-06-12 11:30 ` Jeff Garzik
2009-06-12 19:10 ` Jeff Garzik
2009-06-12 20:26 ` Todd Zullinger
2009-06-12 20:49 ` Jeff Garzik
2009-06-13 15:04 ` Todd Zullinger
2009-06-13 17:22 ` Jeff Garzik [this message]
2009-06-13 17:36 ` Todd Zullinger
2009-06-15 17:23 ` Jeff Garzik
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=4A33E069.4050401@garzik.org \
--to=jeff@garzik.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tmz@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).