Timer Disabling on Package Update? (is: #922031)

Harlan Lieberman-Berg hlieberman at setec.io
Sun Mar 10 17:23:25 GMT 2019


On Sun, Mar 10, 2019 at 1:19 PM Michael Biebl <biebl at debian.org> wrote:
> Let's bump this to serious. I think you should consider making another
> stable upload for this.
> As users have pointed out, systems which aren't rebooted regularly are
> otherwise up for a nasty experience.
> You might consider asking the security team to distribute the update
> with stable-security more quickly and not wait for the next stable upload.

I agree; this needs an update.  I'll open a ticket with the SRMs and
see what they think about it going to -security.

> You have a couple of options to fix this:
> 1/ Switch the compat level back to what 0.10 was using

I think this is the most reasonable approach, since newer versions
aren't using dh_installsystemd anyway.

The bigger question for me is... what do we do about users who have
already upgraded? If my understanding is correct, if we switch back to
compat level 9, they'll all be forcibly started again by the postinst,
correct?  Or do we need to explicitly start it again?

-- 
Harlan Lieberman-Berg
~hlieberman



More information about the Pkg-systemd-maintainers mailing list