git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Jeff Garzik <jeff@garzik.org>
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:36:00 -0400	[thread overview]
Message-ID: <20090613173600.GL5076@inocybe.localdomain> (raw)
In-Reply-To: <4A33E069.4050401@garzik.org>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

Jeff Garzik wrote:
> Found it!  A forgotten package I created, a collective of shell
> scripts, was setting GIT_EXEC_PATH=/usr/local/bin.

Phew.  I was worried I might have to start drinking much earlier than
usual today. ;)

> 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).

Without looking closely at the make files and build logic, is it
perhaps something caused by the previous Fedora git-1.6.0.x packages
passing gitexecdir=%{_bindir} to make, while the F-11 and newer
packages do not set any gitexecdir?

> Things are working again now that the local GIT_EXEC_PATH export is
> removed.

Glad you found the culprit.

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I always keep a supply of stimulant handy in case I see a snake -
which I also keep handy.
    -- W. C. Fields


[-- Attachment #2: Type: application/pgp-signature, Size: 542 bytes --]

  reply	other threads:[~2009-06-13 17:36 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
2009-06-13 17:36               ` Todd Zullinger [this message]
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=20090613173600.GL5076@inocybe.localdomain \
    --to=tmz@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jeff@garzik.org \
    /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).