[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#781334: marked as done (release-notes: add warning about change in perl's handling of unreadable module paths)

Your message dated Sun, 29 Mar 2015 17:18:25 +0200
with message-id <551817C1.8030509@thykier.net>
and subject line Re: Patch
has caused the Debian Bug report #781334,
regarding release-notes: add warning about change in perl's handling of unreadable module paths
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
781334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781334
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: perl
Version: 5.20.2-2
Severity: serious
X-Debbugs-Cc: debian-perl@lists.debian.org

Bug #780830 against spamassassin highlights a 5.18 change in
handling non-readable directories on @INC.

In wheezy (Perl 5.14), 'require' (and therefore 'use' as well) would
skip such entries when searching for modules. The current jessie (5.20)
behaviour will croak on them:

 % perl -I/root -e 'require strict'
 Can't locate strict.pm:   Permission denied at -e line 1.

This may have unfortunate effects if site directories in /usr/local
are not world readable for some reason. The #780830 reporter
had at least one such directory (/usr/local/lib/site_perl), but
it's currently unknown where that came from.

It seems possible to me that /usr/bin/cpan has at some point created such
directories in some configurations, but I haven't really investigated
this. If somebody has non-world-readable @INC directories in /usr/local
and can trace their origins, reports would be welcome. Cc'ing the
debian-perl for likely candidates.

Backporting upstream commit
 http://perl5.git.perl.org/perl.git/commit/e2ce0950e5e4b86c6fcbc488c37dd61d082b3e0d
from 5.21.7 would help a bit as it improves the diagnostics in the
error message by reporting the name of the directory missing permissions.
I'm inclined to add this for jessie but I'd welcome other opinions on this.
Mentioning this in the release notes might also make sense.

Filing as 'serious' for now as I suppose this can be considered a regression
from wheezy.

See also related upstream discussion at
 https://rt.perl.org/Public/Bug/Display.html?id=123795

-- 
Niko Tyni   ntyni@debian.org

--- End Message ---
--- Begin Message --- 
On Fri, 27 Mar 2015 18:11:12 +0000 Dominic Hargreaves <dom@earth.li> wrote:
> Control: retitle -1 release-notes: add warning about change in perl's handling of unreadable module paths
> Control: tags -1 -pending
> Control: tags -1 +patch
> 
> Hi,
> 
> Please see a patch for this issue attached.
> 
> Cheers,
> Dominic.

Thanks for the patch. :)

I have committed it with two minor modifications:

 * Add missing </section>
 * Note that perl -V shows the default @INC path.

Thanks,
~Niels

--- End Message ---
Reply to: