Your message dated Mon, 30 Sep 2019 11:04:10 +0000
with message-id <[email protected]>
and subject line Bug#867263: fixed in dbus 1.12.16-2
has caused the Debian Bug report #867263,
regarding dbus: /var/log/reboot-required.pgks not updated when
/var/log/reboot-required is touched
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
867263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbusVersion: 1.10.20-1Severity: normal
Dear Maintainer
* What led up to the situation?
I upgraded dbus (from 1.10.18-1 to 1.10.20-1) as part of a regular aptitude
upgrade
* What was the outcome of this action?
A message "A reboot is required to replace the running dbus-daemon." was shown
and /var/run/reboot-required was touched, but /var/run/reboot-required.pgks
remained unchanged (absent in this case)
* What outcome did you expect instead?
Additionally to the above, /var/run/reboot-required.pkgs should be used to
identify dbus as the package requesting a reboot.
As a secondary issue, I would vote for a fix for https://bugs.debian.org/805449
but if we do need a reboot, it should be clear why to facilitate an informed
decision about when the reboot should be scheduled
As a tertiary issue, but I can't work out where to report it (pointers
welcome!) the contents of the reboot-required.pkgs file in general could really
do with some more information about the package versions and the timing of the
request - that way I can look at the changelog to see what rebooting will get
me in terms of bugfixes etc. (eg. if if the update fixes a typo in a rare error
message but dbus can't be replaced without a reboot, that reboot is going to
wait until I have a better reason to reboot - if it fixes a major security
issue, that reboot will happen as soon as reasonably possible)
P.S. reportbug let me down so I'm attempting to submit this by email - sorry if
I've missed important information or mucked up the formatting etc.
Cheers & God bless Sam "SammyTheSnake" Penny
--- End Message ---
--- Begin Message ---
Source: dbus
Source-Version: 1.12.16-2
We believe that the bug you reported is fixed in the latest version of
dbus, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated dbus package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 30 Sep 2019 09:33:59 BST
Source: dbus
Binary:
Architecture: source
Version: 1.12.16-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Description:
Closes: 867263
Changes:
dbus (1.12.16-2) unstable; urgency=medium
.
* Add bug number to previous changelog entry
* Standards-Version: 4.4.1 (no changes required)
- Note that dbus-user-session still has its previous dependencies,
and has deliberately not been switched to the new default-logind
virtual package. dbus-user-session relies on systemd --user: it
is not enough to have systemd-logind or a compatible replacement
like elogind.
* d/dbus.init: Work around #940971 in libnss-systemd.
If we are booting with a non-systemd init but libnss-systemd is still
installed, tell libnss-systemd not to try to connect to dbus-daemon,
which is never going to work well from inside dbus-daemon.
* dbus.postinst: Append dbus to /run/reboot-required.pkgs on upgrade
(Closes: #867263)
Checksums-Sha256:
372942bddb9827359683654c5c74b39bb8c18c249d889bf97d9f476a69242f23 3888
dbus_1.12.16-2.dsc
98e396f11fddb075e38464fb25e211894cc92d4ac7cf12c476b94bf18932bd33 64400
dbus_1.12.16-2.debian.tar.xz
4261e3dba799dffaf199f877670ff18f8cd5db64a656d71b434710641e445f80 7378
dbus_1.12.16-2_source.buildinfo
Checksums-Sha1:
7af49bcf7767f61910b8dd02d2998e9f036b47e2 3888 dbus_1.12.16-2.dsc
bef671bfd26165fa785eed3963cb49cc843fa886 64400 dbus_1.12.16-2.debian.tar.xz
bec91f3fb6c64804276a5bb0f2c488d7f6ea80ce 7378 dbus_1.12.16-2_source.buildinfo
Files:
aa02411f68342147e5bdd1198154d7f6 3888 admin optional dbus_1.12.16-2.dsc
ff04d7a39161d3329a12bfe1e0bba513 64400 admin optional
dbus_1.12.16-2.debian.tar.xz
8dcb247653a63008b7569f647bbb198c 7378 admin optional
dbus_1.12.16-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl2R254QHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT19kD/90x5wkfsgkA/oiDczTaOestwRWLH4q39/r
w7mEPRlIdlDAVcgJY33QahlIKp6p09q26Ko1bWQF3iwB4OBFJacdhn3lEfve43e1
aWT2r+rWiIdcROrF6UFNQMPvP3IIdvI9gXijdpEZd6UHSQh69delqUlA4SWpv3Ok
2mcYWdCaSqtIKqd6+/Vhu1YCMz+z4GaHyHQeEhhxFVAD5jYYVDLLzwXxhtNvt0Ey
X/OmjnOAhaoEWK9h2nwF0rqZUcl0X+imSjeyO8zowU1jFX/z28Hr6lgbEk1CCHbW
viXPplPwc8TpLmOnm4ME0APIdFG98RlWBnE7AWFdJFnez7f1vJArV3sGSyKgb794
OTa2pAIO1FApU+gXWVzC5lSXqB6VLNrYg94Pca/JLyGzPKE51M1b9AeA+gZVwiuO
tP/cvzF2ThTRjUR01VYX+4mbyN+/ta/vjYe65HnHp2QoSZxhPtp5Wxtl3BUaPUBX
UBjSaoiPlH0SnI4QCyNI+w0xCiqQ0GWjnkPpUkj8fEBm0BakvMeiQ+GJg1DjlpK9
oRJNs1goGqWWXn9r/7jLA3c2jiFKq43pRoCy561YmgnD8su7VrE6Xxfi3I0DoFOg
b5HlGE5hhR50vIJacogpNyVLogY2nGOqkfEnB/o0kXYKVnfri0BzQiXCp2ukTx5G
8G+zIilgGA==
=EudL
-----END PGP SIGNATURE-----
--- End Message ---
