From: Junio C Hamano <gitster@pobox•com>
To: Johannes Sixt <j6t@kdbg•org>
Cc: Fritz Anderson <fritza@uchicago•edu>,
git@vger•kernel.org, Daniel Barkalow <barkalow@iabervon•org>
Subject: Re: "fatal: index-pack failed" on git-clone
Date: Wed, 08 Jul 2009 15:48:15 -0700 [thread overview]
Message-ID: <7vvdm26bbk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <200907082242.51495.j6t@kdbg.org> (Johannes Sixt's message of "Wed\, 8 Jul 2009 22\:42\:51 +0200")
Johannes Sixt <j6t@kdbg•org> writes:
> However, if Fritz runs 'sudo /usr/local/bin/git clone ...', then the interim
> PATH is "/usr/local/bin:/usr/local/libexec/git-core:/bin:/usr/bin" because
> this time setup_path() finds a non-empty argv0_path, and the command works.
Ahh, that is what I was missing.
As I said elsewhere already, I personally do not think sudo is worth
supporting compared to the cost of this kind of pain resulting from its
misguided "safety" brokenness, but apparently it is widely used. I think
what Peff suggests in this thread might be a reasonable workaround.
next prev parent reply other threads:[~2009-07-08 22:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 15:58 "fatal: index-pack failed" on git-clone Fritz Anderson
2009-07-08 16:42 ` Junio C Hamano
2009-07-08 17:10 ` Fritz Anderson
2009-07-08 17:34 ` Junio C Hamano
2009-07-08 18:22 ` Fritz Anderson
2009-07-08 18:49 ` Junio C Hamano
2009-07-08 19:05 ` Daniel Barkalow
2009-07-08 20:05 ` Fritz Anderson
2009-07-08 20:23 ` Fritz Anderson
2009-07-08 20:42 ` Johannes Sixt
2009-07-08 21:12 ` Jeff King
2009-07-08 21:27 ` Fritz Anderson
2009-07-09 18:11 ` Johannes Sixt
2009-07-08 22:48 ` Junio C Hamano [this message]
2009-07-09 6:37 ` Jeff King
2009-07-09 8:42 ` Michael J Gruber
2009-07-09 23:29 ` A Large Angry SCM
2009-07-13 4:52 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 8:06 Johannes Sixt
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=7vvdm26bbk.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=barkalow@iabervon$(echo .)org \
--cc=fritza@uchicago$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
--cc=j6t@kdbg$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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