Bug#919507: Fw: Packaging policy to flag unattended-upgrades reboot

["Karl O. Pinc" <kop@meme.com>]

Begin forwarded message:

Date: Wed, 16 Jan 2019 18:10:04 -0600
From: "Karl O. Pinc" <kop@meme.com>
To: Michael Vogt <mvo@debian.org>, Balint Reczey <rbalint@ubuntu.com>
Subject: Packaging policy to flag unattended-upgrades reboot


Hello,

Do you have any suggestions for updating the
Debian Policy docs so that packagers know what
must be done to inform when an update requires
a reboot?

I filed the following bugs against debian-policy
and systemd:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919507
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919509
thinking that packages are supposed to provide
breadcrumbs so that unattended-upgrades knows when
a package upgrade requires a reboot.

I've been invited to submit a patch to Debian policy.

But looking at the packaging of packages I _thought_
flagged reboots I don't see anything.

I know the kernel flags a reboot, but see that
unattended-upgrades is dropping a config into
/etc/kernel/postinst.d/.

I thought libc6 flagged a reboot, but can't find
anything.

I've got an email from a box that flagged a
reboot on upgrade of tomcat8, but can't find
anything in the packaging.  Why I got an email is
now a mystery.

I would think that having the unattended-upgrade
package have to keep track of which packages
require reboot would not scale....

Thanks.

Regards,

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein

P.S.  Somebody on #debian-mentors was able to do a
search today for all the packages which, I think,
contained mention of "reboot-required".  I don't
know what they did or how they did it.
There was a list of maybe 15 or 20 packages,
but the remark was that some of these are
tool-related.  (?) I forget the details.




Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein