[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#919507: debian-policy: Policy contains no mention of /var/run/reboot-required


On Wed 16 Jan 2019 at 12:29PM -0600, Karl O. Pinc wrote:

> Recent systemd security updates (
> systemd (232-25+deb9u8) stretch-security; urgency=high,
> systemd (232-25+deb9u7) stretch-security; urgency=high)
> require a system reboot to take effect, but the
> unattended-upgrades did not tell the user to reboot
> (or auto-reboot).
> Apparently /var/run/reboot-required is touched to by
> debian packages to provide notification when an update
> of the package requires a system reboot to take effect.
> https://sources.debian.org/src/unattended-upgrades/1.9/unattended-upgrade/#L83
> "The Internet" says that it is the postinst script which
> is supposed to touch /var/run/reboot-required when a reboot
> is required.
> If Debian supports user notification when reboot is required
> (or automatic rebooting) after automatic upgrade then there
> should be some consistent standard.  And that standard
> should be documented.  Someplace.
> I don't suppose that there are many packages which require
> a reboot to take effect after update, but they are the
> important packages.  The kernel and libc6 packages
> trigger reboot notification, but systemd does not.

It seems fine to document this in Policy.

A patch would be welcome.

Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply to: