Re: Permission denied to module

Since 5.18, when require (and thus, I surmise, use), can't read a file, it dies (perl5180delta.pod):

require dies for unreadable files
When require encounters an unreadable file, it now dies. It used to ignore the file and continue searching the directories in @INC perl #113422.

So maybe you have another directory with an unreadable MIME/Lite.pm in @INC, and that causes the failure?

Comment on Re: Permission denied to module Select or Download Code

Replies are listed 'Best First'.
Re^2: Permission denied to module by dave_the_m (Monsignor) on May 26, 2015 at 22:10 UTC
A common variant on an unreadable file is that the directory which the file may or may not be in is itself unreadable (perl doesn't distinguish between these cases). So the OP likely has PERLLIB or PERL5LIB including an unreadable directory. The almost-released perl-5.22.0 improves the error message by indicating which path failed: `$ export PERLLIB=/root $ perl-5.16.0 -Mstrict -e1 $ perl-5.18.0 -Mstrict -e1 Can't locate strict.pm: Permission denied. $ perl-5.20.0 -Mstrict -e1 Can't locate strict.pm: Permission denied. $ perl5.22.0-RC2 -Mstrict -e1 Can't locate strict.pm: /root/strict.pm: Permission denied.` [download] Dave.	[reply] [d/l]
Re^3: Permission denied to module by zdavek (Initiate) on May 27, 2015 at 14:49 UTC
Yes! That was it! We had PERL5LIB defined in our shell initialization scripts with a directory that was not accessible to most of our users. Thanks.	[reply]