From: Vasiliy Yeremeyev <vayerx@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] Directory probing for aliases
Date: Thu, 11 Oct 2012 14:22:45 +0400 [thread overview]
Message-ID: <CAFKeBpcCZwMMcBtP8KywqnyK3e247K1Z_8na5ah+Wb+E15LPVQ@mail.gmail.com> (raw)
Hi,
Git aliases stop working when user doesn't have permissions to any
directory within $PATH list:
% git config alias.br branch
% git br
fatal: cannot exec 'git-br': Permission denied
Problem seems to be in directories probing:
execve("/usr/libexec/git-core/git-br", ["git-br"], [/* 76 vars */]) =
-1 ENOENT (No such file or directory)
execve("/home/vayerx/bin/git-br", ["git-br"], [/* 76 vars */]) = -1
ENOENT (No such file or directory)
execve("/usr/local/bin/git-br", ["git-br"], [/* 76 vars */]) = -1
ENOENT (No such file or directory)
execve("/usr/bin/git-br", ["git-br"], [/* 76 vars */]) = -1 ENOENT (No
such file or directory)
execve("/bin/git-br", ["git-br"], [/* 76 vars */]) = -1 ENOENT (No
such file or directory)
execve("/opt/bin/git-br", ["git-br"], [/* 76 vars */]) = -1 ENOENT (No
such file or directory)
execve("/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3/git-br", ["git-br"],
[/* 76 vars */]) = -1 ENOENT (No such file or directory)
execve("/usr/games/bin/git-br", ["git-br"], [/* 76 vars */]) = -1
EACCES (Permission denied)
write(2, "fatal: ", 7fatal: ) = 7
write(2, "cannot exec 'git-br': Permission"..., 39cannot exec
'git-br': Permission denied) = 39
(user doesn't have access to '/usr/games/bin' directory)
Everything works fine if '/usr/games/bin' is not listed in $PATH variable.
Standard/built-in git commands work fine regardless of $PATH variable.
--
With Best Regards,
Vasiliy Yeremeyev
next reply other threads:[~2012-10-11 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 10:22 Vasiliy Yeremeyev [this message]
2012-10-11 11:28 ` [BUG] Directory probing for aliases Andreas Schwab
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFKeBpcCZwMMcBtP8KywqnyK3e247K1Z_8na5ah+Wb+E15LPVQ@mail.gmail.com \
--to=vayerx@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).