Re: Bug: git-sh-setup giving no such file or directory
- From
- Paul Boyle <paulcboyle@gmail.com>
- Date
- Dec 9, 2016, 14:00 UTC
- Message-ID
- <CABZ0BffXMOn8eLFwg_o7WsXeRJjB_xd0kNeV1qGiVFPSYbxg+A@mail.gmail.com>
- In-Reply-To
- <20161209134544.z2xbly5xjyito62w@sigill.intra.peff.net>
Show 6 quoted lines
> Hmm. Did you run "make install"? Or are you trying to run git directly > out of the build directory? > > If the latter, that has been unsupported for a while, though it mostly > works. The "right" way is to either set up GIT_EXEC_PATH as appropriate, > or to just .../git/bin-wrappers into your $PATH.
This was the source of it. Root cause, a stupid user ;) I'd a PATH setup to the build directory. Changing the path to bin-wrappers fixed it up.
Thanks!
On Fri, Dec 9, 2016 at 1:45 PM, Jeff King <peff@peff.net> wrote:
Show 40 quoted lines
> On Fri, Dec 09, 2016 at 12:00:36PM +0000, Paul Boyle wrote:
>
>> There appears to be an issue with the latest master.
>>
>> "git submodule init" is producing the following error:
>>
>> /home/paul.boyle/bin/git/git-sh-setup: line 46:
>> /home/paul.boyle/libexec/git-core/git-sh-i18n: No such file or
>> directory
>
> Hmm. Did you run "make install"? Or are you trying to run git directly
> out of the build directory?
>
> If the latter, that has been unsupported for a while, though it mostly
> works. The "right" way is to either set up GIT_EXEC_PATH as appropriate,
> or to just .../git/bin-wrappers into your $PATH.
>
>> Broken sha: 8d7a455ed52e2a96debc080dfc011b6bb00db5d2
>>
>> Checking out an older version works fine.
>>
>> git checkout 'master@{2016-11-01 18:30:00}'
>>
>> Sha: 3cdd5d19178a54d2e51b5098d43b57571241d0ab
>>
>> This can be reproduced simply by:
>>
>> make clean ; make ; git submodule init
>>
>>
>> I didn't track it down further than to a commit sometime in the last month.
>
> You could probably find the exact commit with git-bisect. However, I'd
> be surprised if it is anything but 1073094f3 (git-sh-setup: be explicit
> where to dot-source git-sh-i18n from., 2016-10-29). Before that commit,
> we found git-sh-i18n in the $PATH, which would work if you were adding
> git's build directory to your $PATH (but not work for people who
> actually did an install).
>
> -Peff