On Thu, May 27, 2010 at 05:21:50PM +0100, Ivan Uemlianin wrote:
quoted text
> 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.
 
That looks like you are either running wrong git binary (one in /root/bin?)
or the git installation is busted.

No, the git libexec directory SHOULD NOT be in PATH (git will add it there
when needed).

-Ilari
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html