Bug#858457: spamd stops autostarting after release upgrade

[Robie Basak]

Package: spamassassin
Version: 3.4.0-6
User: pkg-systemd-maintainers at lists.alioth.debian.org
Usertags: systemd-units
X-Debbugs-CC: pkg-systemd-maintainers at lists.alioth.debian.org

If in wheezy I enable spamd by setting ENABLED=1 in
/etc/default/spamassassin, and then I upgrade to jessie, then spamd
stops automatically starting after a reboot due to the switch to
systemd.

Workaround: "systemctl enable spamassassin.service"

I do get a conffile prompt and do see the message telling me about this.
However, various things can suppress that, and the default is usually to
retain the existing configuration.

I wonder if you have an opinion on an upgrade path that detects this
situation in the postinst and enables this automatically if ENABLED=1
was previously set?

I'm reporting this here since we have a report in Ubuntu and it seems
to me to be valid in Debian too. I understand if you do not consider
this to be a bug, and of course once fixed by the user in jessie I don't
expect it to happen again in stretch. This may mean that it isn't
worthwhile fixing even if you consider it valid.

Also see Debian bugs 764438 and 716887.

Downstream bug:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503611
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170322/560625be/attachment.sig>