Your message dated Sun, 30 Sep 2018 10:43:08 -0700
with message-id <[email protected]>
and subject line closing old bug
has caused the Debian Bug report #780830,
regarding spamassassin: Fails to install, 'strict.pm, permission denied'
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 [email protected]
immediately.)
--
780830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780830
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.4.0-6
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Doing a wheezy/jessie upgrade on a virtualbox clone of our server, we
encountered some errors with spamassassin that persisted after a purge and
reinstall. The postinstall errors as below.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Purge, reinstall, and a quick glance at the postinstall script did not point to
anything specific.
Setting up spamassassin (3.4.0-6) ...
Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23.
BEGIN failed--compilation aborted at /usr/bin/sa-update line 23.
dpkg: error processing package spamassassin (--configure):
subprocess installed post-installation script returned error exit status 13
dpkg: dependency problems prevent configuration of sa-compile:
sa-compile depends on spamassassin (>= 3.3.2-8); however:
Package spamassassin is not configured yet.
dpkg: error processing package sa-compile (--configure):
dependency problems - leaving unconfigured
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages spamassassin depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.22
pn libarchive-tar-perl <none>
ii libhtml-parser-perl 3.71-1+b3
ii libnet-dns-perl 0.81-2
ii libnetaddr-ip-perl 4.075+dfsg-1+b1
ii libsocket6-perl 0.25-1+b1
ii libsys-hostname-long-perl 1.4-3
ii libwww-perl 6.08-1
ii perl 5.20.2-2
ii perl-modules [libio-zlib-perl] 5.20.2-2
Versions of packages spamassassin recommends:
ii gnupg 1.4.18-7
ii libio-socket-inet6-perl 2.72-1
ii libmail-spf-perl 2.9.0-3
ii perl [libsys-syslog-perl] 5.20.2-2
iu sa-compile 3.4.0-6
ii spamc 3.4.0-6
Versions of packages spamassassin suggests:
ii libdbi-perl 1.631-3+b1
ii libio-socket-ssl-perl 2.002-2
ii libmail-dkim-perl 0.40-1
ii perl [libcompress-zlib-perl] 5.20.2-2
ii pyzor 1:0.5.0-2
ii razor 1:2.85-4.1+b1
-- debconf-show failed
--- End Message ---
--- Begin Message ---
This issue is quite old and hasn't seen any progress in 3.5 years. With
no additional reports of these symptoms, I believe this must have
somehow been a local issue, I don't think we have any need to keep it
open.
Please reopen if any of the above is inaccurate.
signature.asc
Description: PGP signature
--- End Message ---
