Hi Dimitri, > As per https://wiki.ubuntu.com/UpstartCompatibleInitScripts and the > debian policy on alternative init systems, init.d scripts and upstart > jobs should have a one-to-one mapping by name. > It appears that ceph-all.conf is shipped, but no equivalent init.d > script is present (even a dummy one), therefore the postinstall is > failing if the host system's pid one at the time is not upstart.
> Either guard the calls in the postinst, to check for upstart, or > provide dummy / empty ceph-all initscript. Is it okay to raise the severity of this issue to serious? It leaves my package manager in unconsistent state I'm not able to successfully install or uninstall this package and on each upgrade I get an error saying ceph configure failed. Also its been a month and I'm not seeing any activity on this bug probably because mail is not making it to the moderated list of ceph team. And yes I'm using systemd. -- Vasudev Kamath http://copyninja.info Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net} IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net} GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: PGP signature
