[Pkg-systemd-maintainers] Bug#722521: Bug#722521: Fails to properly re-enable service on install-remove-install sequence

Michael Stapelberg stapelberg at debian.org
Thu Sep 12 05:59:23 BST 2013


Hi Michael,

Michael Biebl <biebl at debian.org> writes:
> to reproduce the problem, do the following steps:
> 1/ apt-get install rsyslog
>    → symlinks are properly created
> # find systemd/ -name "*syslog*"
> systemd/system/multi-user.target.wants/rsyslog.service
> systemd/system/syslog.service
>
> 2/ apt-get remove rsyslog
>    → symlinks are removed
> # apt-get remove rsyslog
> [..]
> rm '/etc/systemd/system/multi-user.target.wants/rsyslog.service'
> rm '/etc/systemd/system/syslog.service'
>
> 3/ apt-get install rsyslog
>    → symlinks are not re-created
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
:). 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?

-- 
Best regards,
Michael




More information about the Pkg-systemd-maintainers mailing list