Bug#919509: systemd packaging does not touch /var/run/reboot-required
biebl at debian.org
Thu Feb 28 18:55:59 GMT 2019
Control: severity -1 wishlist
On Wed, 16 Jan 2019 12:44:28 -0600 "Karl O. Pinc" <kop at meme.com> wrote:
> Package: systemd
> Version: 232-25+deb9u8
> Severity: normal
> systemd security updates to stable
> systemd (232-25+deb9u8) stretch-security; urgency=high
> systemd (232-25+deb9u7) stretch-security; urgency=high
> required reboot to take effect, but /var/run/reboot-required
> was not `touch`ed. Therefore the unattended-upgrades
> package did not notify the user that a reboot is required.
> (There were related upgrades to udev and other packages.)
> There are probably many systems which installed the
> upgrade automatically but did not reboot and so the
> patch did not take effect.
> "The Internet" says that it is the postinst script which
> should touch /var/run/reboot-required.
This should probably be /run/reboot-required, /var/run is a symlink to /run.
That said, an update of the systemd package does not strictly require a
reboot of the system. We do reexec PID 1 and restart all binaries
(besides logind), so I'm a bit undecided if we should actually trigger
that message or not.
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...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers