Andreas Schwab wrote:
> Jim Meyering <j...@meyering.net> writes:
>> Andreas Schwab wrote:
>>> Jim Meyering <j...@meyering.net> writes:
>>>> It is warning you that you have a search PATH containing an
>>>> other-writable directory.
>>>
>>> Nope, I don't.
>>
>> Group-writable?
>
> Nope.
>
>> Can you give me some way to reproduce the failure that
>> involves only directories with proper permissions?
>
> /usr/bin/build coreutils.spec
Thanks, but I don't have /usr/bin/build, and
"yum whatprovides /usr/bin/build" doesn't know about it.
Should I be inferring that it's failing in a chroot for you?
The only time I've been able to evoke that diagnostic from Perl
is when there truly has been an insecure directory in PATH.
If you've found a way to evoke it when there is no such
problem, then it is surely a bug in Perl (not likely, imho).
What I meant was this:
Can you provide a stand-alone set-up similar to the following, with
directories on your PATH (whose perms and ancestor perms are all ok)
that still fails:
perl -Te '$ENV{PATH}=~/(.*)/;$ENV{PATH}="$1";`/bin/true`'
