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

[Michael Biebl]

Am 10.03.19 um 18:23 schrieb Harlan Lieberman-Berg:
> 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?
> 

debhelper should generate code which starts certbot.timer in postinst.

Please double check the generated postinst to be sure.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190310/f88190c5/attachment-0001.sig>