The second bug is fixed in the mentioned Debian bug, and the recent
merge that went in for Xenial has this one fixed for Ubuntu as well.
The first reported issue is something else:
I retried this on the following paths
In each I configured spam assassin checked that it works as intended.
Trusty:
The trusty systems needed ENABLED=1 in /etc/default/spamassassin as intended.
Note: This was not an upstart job yet, only sysv in /etc/init.d/spamassassin
Wily:
On Wily as the config file states "systemctl enable spamassassin.service" is
required - it will then properly start on either next reboot or a manual
"systemctl start spamassassin.service". Afterwards on reboots the service came
up just correctly.
Everything fine and correct so far.
This defined the starting scenario for the upgrades.
Spamassassin after upgrade
14.04 -> 15.10: not started
14.04 -> 16.04: not started
15.10 -> 16.04: started ok
It seems we "just" need a postinst that transfers the old config, if
ENABLED was set to one runs "systemctl enable spamassassin.service".
Since an easy workaround is available it is "only" medium severity, yet
it is a regression on upgrading so not lower.
** Changed in: spamassassin (Ubuntu)
Status: Confirmed => Triaged
** Changed in: spamassassin (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503611
Title:
systemd: spamassassin not starting after upgrading to 15.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503611/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
