Am 12.09.2013 06:59, schrieb Michael Stapelberg: > The reason is that “deb-systemd-helper was-enabled” returns false > after the “apt-get remove rsyslog”, therefore the postinst will not call > “deb-systemd-helper enable” when installing in step 3/. > > I’d argue that this is expected behavior, given that in postrm we run > “deb-systemd-helper disable”. Now the question is why we do that
Actually, I don't know / remember why we changed it that way. I don't think previous versions did that. Do you find a clue in the git log? > :). Especially with regards to #714903 it occurs to me that masking the > files instead of disabling (= removing the symlinks) is the better > alternative here. What do you think? Masking the service might be better indeed, especially as systemctl disable will now also forward the request to update-rc.d, which is kinda odd, that the addition of a systemd service changes the behaviour of the SysV init script on remove. Sounds to me, as if we should drop the "disable-on-remove" bits in i-s-h again, and follow up at #714903 whether and how to use mask and what we need to consider when doing that. Michael -- 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
