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

Bug#919507: Reboot required patch for Debian policy


Attached is: reboot_required_v2.patch

On Thu, 17 Jan 2019 09:10:16 -0600
"Karl O. Pinc" <kop@meme.com> wrote:

> Documents /var/run/reboot-required and
> /var/run/reboot-required.pkgs.

Like v1 of the patch but adds index entries.
It's not clear if this is desirable because
they would be the only index entries.


Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein
diff --git a/policy/ch-maintainerscripts.rst b/policy/ch-maintainerscripts.rst
index 707f2d4..5942123 100644
--- a/policy/ch-maintainerscripts.rst
+++ b/policy/ch-maintainerscripts.rst
@@ -92,6 +92,32 @@ for failure, since the package management system looks for the exit
 status of these scripts and determines what action to take next based on
 that datum.
+.. index::
+   pair: signaling; reboot
+.. _s-signalingreboot
+Signaling that a reboot is required
+.. index::
+   single: reboot-required
+   single: reboot-required.pkgs
+Maintainer scripts can signal that a reboot is required to fully apply
+the changes to the system by touching ``/var/run/reboot-required`` and
+adding the package name to
+``/var/run/reboot-required.pkgs``. Maintainer scripts should not add
+the package name to ``/var/run/reboot-required.pkgs`` if it is already
+present there.
+The appropriate place to do this is expected to be when the
+``postinst`` script is called as ``postinst configure
+Ordinary programs may manipulate these files to signal that a reboot
+is required.
 .. _s-mscriptsinstact:
 Summary of ways maintainer scripts are called

Reply to: