git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Strangely hosed git install
Date: Thu, 28 May 2009 10:29:54 +0200	[thread overview]
Message-ID: <4A1E4B82.9040809@drmicha.warpmail.net> (raw)
In-Reply-To: <46a038f90905280022s1c07565bnf26335fccf7c7e94@mail.gmail.com>

Martin Langhoff venit, vidit, dixit 28.05.2009 09:22:
> On Thu, May 28, 2009 at 9:18 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> "type --all git"?
>> "git --exec-path"?
>> "ls $(git --exec-path)"?
>>
> 
> It all looks fairly correct to me:

Yes, but your shell seems to find git-diff somewhere, so what about:

type --all git-diff
echo $PATH

In any case, Ubuntu seems to do something strange about binaries which
used to be installed. How can "git-diff" trigger a message about
"apt-get install git-core"?

For sure it does the same strange thing for everything else which used
to be in your PATH, and this makes current stash, gc etc. fail when
trying to call git-pack-objects and such. A "/usr/bin time machine"???

OTOH: The git-pack-objects usage line indicates that you clearly have
older plumbing lying around. I suspect there are at least 2 issues on
that box.

Michael

  reply	other threads:[~2009-05-28  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  7:08 Strangely hosed git install Martin Langhoff
2009-05-28  7:18 ` Junio C Hamano
2009-05-28  7:22   ` Martin Langhoff
2009-05-28  8:29     ` Michael J Gruber [this message]
2009-05-28  9:34       ` Martin Langhoff
2009-05-28  9:39         ` Martin Langhoff
2009-05-28  9:47         ` Michael J Gruber
2009-05-28 10:11           ` Martin Langhoff

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=4A1E4B82.9040809@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.langhoff@gmail.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).