[Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
Launchpad Bug Tracker
1823070 at bugs.launchpad.net
Fri Jul 12 02:04:36 UTC 2019
This bug was fixed in the package unattended-upgrades - 1.13
---------------
unattended-upgrades (1.13) unstable; urgency=medium
[ Alban VIDAL ]
* Update french translation.
Signed-off-by: Alban VIDAL <alban.vidal at zordhak.fr>
[ Balint Reczey ]
* Don't crash collecting transitive dependencies when package has no
candidate (LP: #1825886)
* Use mark_install_adjusted() in rewind_cache()
The original cache had packages marked with adjustments thus rewinding
should also do adjustments to reach the same state. Not using
mark_install_adjusted() also crashes when apt raises error on held
packages. (LP: #1826157)
* test_rewind: Update test to check if adjustend rewinding took place
* Only allow removals in valid autoremoval sets
* Fix one more log location in the man page (Closes: #928601)
* Factor out kernel regexp generation to functions
* Packages including kernel version without flavor in their name may be
kernel packages. Also add autopkgtest for checking if the generated
patterns cover the currently running kernel. (LP: #1828200)
* Skip upgrade-all-security test when there are no updates to test with.
Shortly after a release there may not be security updates against the
packages used in the chroot used for the test.
* Test with latest stable in upgrade-all-security on testing
* Fix testing Debian's updates in upgrade-all-security
* Store list of kept packages and report the number of them in motd
(LP: #1823070)
* Mention APT's apt-daily-upgrade.service in the man page
* 50unattended-upgrades.md5sum add MD5 of current files
* PEP8: Fix breaking line after binary operator
* debian/tests/control: Fix Depends: of upgrade-between-snapshots
* debian/tests/control: Allow stderr in kernel-patterns
[ Gordon Lack ]
* Replace boolean Unattended-Upgrade::MailOnlyOnError2 mail reporting setting
with multi-valued (string) Unattended-Upgrade::MailReport.
[ Jaime Hablutzel ]
* Error message improved on very improbable condition
[ Clint Armstrong ]
* Fix showing multi-line strings on Plymouth.
When unattended-upgrades sends it's status to plymouth it sends a
multi-line string which causes plymouth to display overlapping text,
because plymouth only scrolls one line when the message is sent.
(LP: 1826406)
-- Balint Reczey <rbalint at ubuntu.com> Mon, 08 Jul 2019 11:08:30 +0200
** Changed in: unattended-upgrades (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unattended-upgrades in Ubuntu.
https://bugs.launchpad.net/bugs/1823070
Title:
unattended-upgrades should tell the user (via motd) when security
updates are held back
Status in unattended-upgrades package in Ubuntu:
Fix Released
Bug description:
Currently we have the following pieces as part of the default UX on
Ubuntu 18.04 and later:
1) unattended-upgrades automatically installs security updates daily by default
2) the motd reports the number of available updates, including security updates.
A user who knows about 1) also knows that a non-zero number of pending
security updates listed in 2) is nothing to worry about.
However, unattended-upgrades will also cleverly detect when a security
update cannot safely be installed non-interactively due to conffile
changes on the system.
In this case, unattended-upgrades should also inform the user via the
motd that these updates are not being installed. Otherwise, there's
nothing to tell the user that the non-zero count of available security
updates in motd is a *problem*.
Suggested wording:
N security updates will not be automatically installed due to local changes.
See /var/log/foo for details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+subscriptions
More information about the foundations-bugs
mailing list