Am 08.11.2014 um 16:41 schrieb Michael Meskes: > On Wed, Nov 05, 2014 at 02:04:29PM +0100, Michael Biebl wrote: >> That's a decision that's up to the maintainer. > > Thanks for the explanation. That change in question was provided as a patch > back in the day and to the day I hadn't even noticed that acpid wasn't > running.
Hm, ok. It's unfortunate that the effect of this patch was not properly communicated and not clear on your side. I think it's useful to retain the ability to have acpid socket activated, so it's only started on demand for those users, who don't need it running always. So I'd like to keep this option. Regarding this particular bug, here are some suggestions how you could address it: a/ Keep the status quo of the package, but document the changed behaviour prominently in NEWS.Debian. I.e., people upgrading from wheezy will get a notification and instructions to run "systemctl enable acpid.service" manually if they want an always running acpid (under systemd). b/ Enable both .socket and .service units upon installation and add a note to README.Debian, that the .service unit can be disabled manually if one want's starting-on-demand behaviour. For that, you'd need to remove the --no-enable switch from the override in debian/rules. c/ Enable the .service unit on upgrades only. This would need to be done manually in postinst, dh_systemd can not automate that. If you keep the socket activation option, I'd also suggest to use --restart-after-upgrade for the acpid service. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
