So it looks like the DCC module is no longer being loaded, but the
spamassassin general configuration still has dcc directives. Apache has
a similar potential situation, but there the configuration directives
specific about a module are surrounded by ifdef/endif delimiters, to
only try to attempt those configurations if the module is loaded. If
spamassassin had something like this, we could use it. Otherwise, it
feels like a local configuration error where the module was disabled in
the upgrade.
Let's see if someone can try a release upgrade with spamassassin configured
like that, to see if at least a dpkg conf prompt is issued (it should).
** Tags removed: server-triage-discuss
** Tags added: server-todo
** Changed in: spamassassin (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2164733
Title:
package sa-compile 4.0.2-3 failed to install/upgrade: old sa-compile
package postinst maintainer script subprocess failed with exit status
255
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2164733/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
