Re: aliases causing “Permission denied” error in git v1.7

From: Jeff King <peff@peff.net>
Date: Nov 4, 2011, 20:34 UTC
Message-ID: <20111104203415.GB26591@sigill.intra.peff.net>
In-Reply-To: <CALUFZ3n9cpHw3r3rcGriDqvJ+UM83L3Q19m=0YeAy51LBJzosA@mail.gmail.com>

On Fri, Nov 04, 2011 at 12:09:07PM +0400, Алексей Данченков wrote:

> $ git co -b newbranch
> $ git co oldbranch
> 
> results in "fatal: cannot exec 'git-co': Permission denied" error.

Git will try commands in your PATH before aliases. So you are running into a permissions problem with a "git-co" in your PATH.

Or more likely, there is an inaccessible directory of your PATH (and we get the same error code from execve whether it is the directory or the file itself which lacks permission). Try "git foobar" and I suspect you will see the same thing (it doesn't matter that you have no foobar alias; we never get past the "try to exec it" stage).

If you are on Linux, try:

  strace -f -e execve git foobar

to see the the problematic entry that is returning EACCES. Or look through your $PATH manually.

-Peff