[rt.cpan.org #95624] cpan as root cannot install Inline without force
Tue Jun 24 05:08:35 2014: Request 95624 was acted upon. Transaction: Correspondence added by SISYPHUS Queue: Inline Subject: cpan as root cannot install Inline without force Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: jeff.ja...@gmail.com Status: open Ticket URL: https://rt.cpan.org/Ticket/Display.html?id=95624 Fixed as of 0.55_01
[rt.cpan.org #95624] cpan as root cannot install Inline without force
Thu Jun 12 04:34:47 2014: Request 95624 was acted upon. Transaction: Correspondence added by ETJ Queue: Inline Subject: cpan as root cannot install Inline without force Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: jeff.ja...@gmail.com Status: new Ticket URL: https://rt.cpan.org/Ticket/Display.html?id=95624 I'd be very interested to know whether the change proposed in https://github.com/mohawk2/inline-pm/commit/f9242a2e92244d99a2ce051c9ae523913eb47fc4 fixes this issue.
Re: [rt.cpan.org #95624] cpan as root cannot install Inline without force
-Original Message- From: Reini Urban It makes sense that this happens, because of course /usr/bin/ is writable by root. Thanks. We need to skip those TAINT checks if run as root or Windows Administrator. You mean that we have 08taint.t check to see whether it's being run as root/administrator ... and if it is then it skips all tests ? That sounds ok to me (assuming it's possible to reliably detect the case). Is it *guaranteed* that Inline won't work under -T when run as root/admin ? Or is it merely *possible* that Inline won't work under -T when run as root/admin ? (The answer has a bearing on the SKIP message that we would present, and upon the modification we would make to the TAINT documentation that we provide.) Patch welcome. Does anyone actually use -T and Inline ? If so, do they use it safely ? Cheers, Rob
[rt.cpan.org #95624] cpan as root cannot install Inline without force
Tue May 13 17:21:02 2014: Request 95624 was acted upon. Transaction: Ticket created by jeff.ja...@gmail.com Queue: Inline Subject: cpan as root cannot install Inline without force Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: jeff.ja...@gmail.com Status: new Ticket URL: https://rt.cpan.org/Ticket/Display.html?id=95624 on CentOS6.5, perl 5.10.1, I cannot install Inline using cpan Inline /dev/null. I can install it with cpan -f Inline /dev/null, but that is less than optimal. The problem seems to be the same one as reported here: https://rt.cpan.org/Public/Bug/Display.html?id=65703 The taint test fails because the directory containing 'make' is removed from $ENV{PATH}. It makes sense that this happens, because of course /usr/bin/ is writable by root. But then does that mean it is just unsupported to install through cpan as root on any linux system? If that is the case, I think I would have found more documentation or complaints about that. Or is the test script supposed to give away rights, and that is not working for me for some reason? Thanks, Jeff
Re: [rt.cpan.org #95624] cpan as root cannot install Inline without force
On 05/13/2014 04:21 PM, jeff.ja...@gmail.com via RT wrote: Tue May 13 17:21:02 2014: Request 95624 was acted upon. Transaction: Ticket created by jeff.ja...@gmail.com Queue: Inline Subject: cpan as root cannot install Inline without force Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: jeff.ja...@gmail.com Status: new Ticket URL: https://rt.cpan.org/Ticket/Display.html?id=95624 on CentOS6.5, perl 5.10.1, I cannot install Inline using cpan Inline /dev/null. I can install it with cpan -f Inline /dev/null, but that is less than optimal. The problem seems to be the same one as reported here: https://rt.cpan.org/Public/Bug/Display.html?id=65703 The taint test fails because the directory containing 'make' is removed from $ENV{PATH}. It makes sense that this happens, because of course /usr/bin/ is writable by root. But then does that mean it is just unsupported to install through cpan as root on any linux system? If that is the case, I think I would have found more documentation or complaints about that. Thanks. We need to skip those TAINT checks if run as root or Windows Administrator. Or is the test script supposed to give away rights, and that is not working for me for some reason?