On Sat, 09 Feb 2019 17:59:18 -0700
Sean Whitton wrote:
> >> The ``/run/reboot-required`` mechanism is used when a reboot is
> >> needed to fully apply the changes introduced by a package
> >> installation or upgrade. Typically it is the ``postinst``
> >> maintainer script that to
Hi Sean,
On Sun, 20 Jan 2019 15:02:05 -0700
Sean Whitton wrote:
> > It is clear to me that a reboot will occur whenever
> > /var/run/reboot-required exists, regardless of the
> > state of /var/run/reboot-required.pkgs.
> >
> > It is not clear to me where reboot-required.pkgs is used.
>
> Your
On Sat, 19 Jan 2019 11:10:09 -0700
Sean Whitton wrote:
> On Fri 18 Jan 2019 at 12:04PM -0600, Karl O. Pinc wrote:
> > +Maintainer scripts can signal that a reboot is required to fully
> > apply +the changes to the system by touching
> > ``/run/reboot-required`` and +addin
On Fri, 18 Jan 2019 09:35:05 -0300
Felipe Sateler wrote:
> /var/run is a compatibility symlink to /run. This paragraph should
> reference /run directly.
Fixed in attached patch: reboot_required_v3.patch
Regards,
Karl
Free Software: "You don't pay back, you pay forward."
-- R
Hi,
Attached is: reboot_required_v2.patch
On Thu, 17 Jan 2019 09:10:16 -0600
"Karl O. Pinc" 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 wo
Hi,
Attached is: reboot_required_v1.patch
Documents /var/run/reboot-required and
/var/run/reboot-required.pkgs.
Regards,
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
diff --git a/policy/ch-maintainerscripts.rst b/policy/ch-maintainerscripts
On Thu, 17 Jan 2019 13:31:56 +0500
Andrey Rahmatullin wrote:
> On Wed, Jan 16, 2019 at 06:13:17PM -0600, Karl O. Pinc wrote:
> > P.S. Somebody on #debian-mentors was able to do a
> > search today for all the packages which, I think,
> > contained mention of "reboot-re
On Wed, 16 Jan 2019 15:28:05 -0700
Sean Whitton wrote:
> > 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.
> It seems fine
Begin forwarded message:
Date: Wed, 16 Jan 2019 18:10:04 -0600
From: "Karl O. Pinc"
To: Michael Vogt , Balint Reczey
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
mu
Hi,
Here is the corresponding bug report on systemd:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919509
Regards,
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Package: debian-policy
Version: 3.9.8.0
Severity: normal
Hi,
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
11 matches
Mail list logo
