On Mon, Mar 23, 2015 at 10:24:50AM +0100, Kasper Loopstra wrote: > >> Setting up spamassassin (3.4.0-6) ... > >> Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23. > > I assume you have a restricted directory on the default Perl search path > > (@INC) that the debian-spamd user can't read, probably under /usr/local ? > > (See "perl -V" for the list of directories on @INC). > This is correct, in /usr/local/lib/site_perl. Should these be > world-readable? I am not that familiar with Perl (beyond editing some > specific scripts).
Yes, it looks like they should be world readable, although I'd be interested in knowing why they aren't. Also, just /usr/local/lib/site_perl doesn't explain your problem as strict.pm should be earlier on the search path. Is /etc/perl, /usr/local/share/perl, /usr/local/lib, or something like that non-readable too? Does /usr/share/perl/5.20/strict.pm exist? > After some chmod o+r and +x on directories listed in > perl -V, I'm getting new errors: > > Setting up spamassassin (3.4.0-6) > /usr/bin/perl: error while loading shared libraries: libperl.so.5.20: > cannot open shared object file: No such file or directory This is worse than it was when you started. It looks like you either removed permissions somewhere instead of adding them, or your file system is getting corrupted somehow. The file libperl.so.5.20 should be in /usr/lib/x86_64-linux-gnu and world readable. > I am not exactly sure what permissions should be on what files. Any > ideas on how to recover this systems Perl back to a usable state? Generally the directories should me root:root, mode 755. For reference, this is how the @INC permissions and symlinks look on my system: drwxr-xr-x 5 root root 4096 Oct 5 2013 /etc/perl lrwxrwxrwx 1 root root 6 Feb 27 20:14 /usr/lib/x86_64-linux-gnu/perl/5.20 -> 5.20.2 drwxr-xr-x 32 root root 4096 Mar 1 20:47 /usr/lib/x86_64-linux-gnu/perl/5.20.2 drwxr-xr-x 93 root root 4096 Mar 21 21:16 /usr/lib/x86_64-linux-gnu/perl5/5.20 drwxr-xr-x 189 root root 12288 Feb 28 00:22 /usr/share/perl5 lrwxrwxrwx 1 root root 6 Feb 27 20:14 /usr/share/perl/5.20 -> 5.20.2 drwxr-xr-x 58 root root 12288 Mar 1 20:47 /usr/share/perl/5.20.2 but if you've changed other permissions as well, it becomes rather hard to help. Possibly the best start is to reinstall perl, perl-base, perl-modules, and libperl5.20 with dpkg. > Or should we postpone further testing of the jessie upgrade path until a > new version of Perl becomes available in testing? Will that happen > before release? No, there are currently no plans to update Perl in any major way before the jessie release. > As far as I know, the system we're using never had any special Perl > stuff happening to it, but it has been upgraded from squeeze (or maybe > etch) over the last years. Should I raise a bug with the perl package? I'm not yet convinced this is a perl bug rather than a local problem. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
