From: Jeff King <peff@peff.net>
To: Ivan Uemlianin <ivan@llaisdy.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git pull works remotely but not locally
Date: Thu, 27 May 2010 11:38:12 -0400 [thread overview]
Message-ID: <20100527153812.GA23484@coredump.intra.peff.net> (raw)
In-Reply-To: <4BFE8DF8.8050301@llaisdy.com>
On Thu, May 27, 2010 at 04:21:28PM +0100, Ivan Uemlianin wrote:
> Thanks for your comment.
> >What happens if you run "git pull"? If you get an error, can you try to
> >run "GIT_TRACE=1 git pull"? Git should then print out exactly what it is
> >trying to exec that is failing.
>
> Not very exciting:
>
> $ GIT_TRACE=1 git pull
> trace: exec: 'git-pull'
> trace: run_command: 'git-pull'
> fatal: cannot exec 'git-pull': Permission denied
Then the next thing to try is probably (assuming you are running Linux):
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.
-Peff
next prev parent reply other threads:[~2010-05-27 15:38 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 [this message]
2010-05-27 16:21 ` Ivan Uemlianin
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=20100527153812.GA23484@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=ivan@llaisdy.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).