From: Ivan Uemlianin <ivan@llaisdy•com>
To: unlisted-recipients:; (no To-header on input)
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: git pull works remotely but not locally
Date: Thu, 27 May 2010 17:21:50 +0100 [thread overview]
Message-ID: <4BFE9C1E.7050308@llaisdy.com> (raw)
In-Reply-To: <20100527153812.GA23484@coredump.intra.peff.net>
On 27/05/2010 16:38, Jeff King wrote:
> Then the next thing to try is probably (assuming you are running Linux):
>
Well, kind of: it's CentOS, which I'm finding quite recalcitrant (e.g. I
had to install strace).
> strace -f -e execve git pull
>
> Though I suspect we may just see:
>
> execve("/opt/libexec/git-core/git-core/git-pull", ...) = -1 EACCES (Permission denied)
>
> which doesn't help much. I just want to be sure that is the source of
> the problem.
>
No, the output is interesting. The permissions denied is from the
erroneous /root install (see separate email):
[pid 3485] execve("/root/libexec/git-core/git-pull", ["git-pull"],
[/* 18 vars */]) = -1 EACCES (Permission denied)
It looks in /opt/bin, but not /opt/libexec.
It could be a botched git install or it could be a botched PATH --- I
have had to fiddle about with it a bit. For example, /opt/libexec is
not on my PATH ... In fact my PATH *is* botched:
$ $PATH
bash: /opt/bin:<snip/>:/usr/bin:/root/bin: No such file or directory
Those last two items don't look good at all. And:
$ PATH=/opt/libexec/git-core/:$PATH
$ git pull
remote: Counting objects: 8, done.
...
1 files changed, 2 insertions(+), 1 deletions(-)
Working!
So:
- git itself is probably OK
- I have a botched PATH, which I should fix asap
Does git expect certain paths to be on a user's PATH? If so perhaps
that is all that is wrong.
Best wishes
Ivan
--
============================================================
Ivan A. Uemlianin
Speech Technology Research and Development
ivan@llaisdy•com
www.llaisdy.com
llaisdy.wordpress.com
www.linkedin.com/in/ivanuemlianin
"Froh, froh! Wie seine Sonnen, seine Sonnen fliegen"
(Schiller, Beethoven)
============================================================
next prev parent reply other threads:[~2010-05-27 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 13:35 git pull works remotely but not locally Ivan Uemlianin
2010-05-27 14:20 ` Ramkumar Ramachandra
2010-05-27 14:37 ` Ivan Uemlianin
2010-05-27 14:47 ` Sverre Rabbelier
2010-05-27 15:07 ` Ivan Uemlianin
2010-05-27 15:15 ` Jeff King
2010-05-27 15:21 ` Ivan Uemlianin
2010-05-27 15:28 ` Johannes Sixt
2010-05-27 15:37 ` Ivan Uemlianin
2010-05-27 15:38 ` Jeff King
2010-05-27 16:21 ` Ivan Uemlianin [this message]
2010-05-27 16:57 ` Ilari Liusvaara
2010-05-27 15:15 ` Ramkumar Ramachandra
2010-05-27 15:36 ` Ivan Uemlianin
2010-05-27 19:53 ` Johannes Sixt
2010-05-28 8:24 ` Ivan Uemlianin
2010-05-27 14:50 ` Ramkumar Ramachandra
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=4BFE9C1E.7050308@llaisdy.com \
--to=ivan@llaisdy$(echo .)com \
--cc=git@vger$(echo .)kernel.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