Package: mailavenger Version: 0.8.5-1 Severity: normal Hi Dererk,
As mentioned in #931085, I noticed that mailavenger now installs a systemd unit file, which causes it to try to run the mailavenger daemon during the install. If one has not already provided a configuration, this fails, which is not surprising given that you say in the README that one would need to do that first. However it is a change from the old behaviour where sysvinit would avoid trying to start it until one had edited the /etc/defaults file. In order to get past this for the CI test pipeline provided by salsa, I patched things to avoid the postinst installing the unit enabled: https://salsa.debian.org/philh/mailavenger/commit/3f6d7f657ca1c9bfe92cb908040bab91453fc9e3 which does allow it to be installed for the autopkgtest test, but is not a complete solution to the problem, because there needs to be something to detect that the package is being installed as an upgrade from a version that was relying on sysvinit, and where the local admin has configured and enabled mailavenger to run at boot time, in which case one would then want to enable the systemd unit to ensure that that continued to be the case under systemd. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
