[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
Launchpad Bug Tracker
1624644 at bugs.launchpad.net
Thu Mar 1 16:32:49 UTC 2018
This bug was fixed in the package unattended-upgrades - 1.0ubuntu1
---------------
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
- Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
unattended-upgrades (1.0) unstable; urgency=medium
[ Simon Arlott ]
* Revert sending mails on WARNINGS when in MailOnlyOnError mode"
* Consider conffile prompts to be errors (Closes: #852465)
Flag packages that have to be upgraded manually because of a conffile
prompt and consider this to be an error when sending email or exiting.
[ Simon McVittie ]
* Add python, python3, setuptools, DistutilsExtra to Build-Depends.
They are needed for `clean`, so Build-Depends-Indep is not enough.
* Add .gitignore and debian/.gitignore
* Remove bzr configuration.
This is unnecessary now that u-u is in git.
[ Michael Vogt ]
* unattended-upgrades: tweak mail-on-warnings PR
* unattended-upgrade: extract is_autoremove_valid helper
[ Balint Reczey ]
* Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
* Clean up processes started for getting md5 sums
* Don't keep /var/lib/dpkg/status open multiple times
* Adjust candidates in UnattendedUpgradesCache.open()
* Perform autoremovals in minimal steps, too.
Also add check to remove only the set of packages selected for autoremoval.
Without that check unattended-upgrades when (by default) configured to
remove newly unused packages could also remove auto removable packages
which were unused before starting starting the upgrade step.
* Remove unused automatically installed kernel packages
(LP: #1357093, #1624644, #1675079, #1698159)
* Stop including Python syntax in the report (Closes: #876796)
* Do not auto remove packages related to the running kernel (LP: #1615381)
* Check packages to be autoremoved against blacklists, whitelists.
Also check if the packages are held.
* Report package removals in the summary email (Closes: #876797)
* Run upgrade-between-snapshots test with debugging enabled
* Don't create new UnattendedUpgradesCache for checking for autoremovals
.open() refreshes the state in each cache_commit(), this is enough
* Update .pot and .po files
* Update .travis.yml to actually build and test u-u from the repo
* Run only a simple installation test on Travis, the system upgrade
test was always failing
-- Balint Reczey <rbalint at ubuntu.com> Thu, 01 Mar 2018 17:29:33 +0700
** Changed in: unattended-upgrades (Ubuntu)
Status: Fix Committed => 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/1624644
Title:
By default settings unattended-upgrade does not automatically remove
packages that become unused in conjunction with updating by other
software
Status in apt package in Ubuntu:
Confirmed
Status in gnome-software package in Ubuntu:
Invalid
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
In Progress
Status in apt source package in Artful:
Confirmed
Status in gnome-software source package in Artful:
Invalid
Status in unattended-upgrades source package in Artful:
In Progress
Status in update-manager source package in Artful:
In Progress
Bug description:
When using default settings for unattended-upgrade i.e.
Unattended-Upgrade::Remove-Unused-Dependencies "false";
# default "false"
Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
# default "true"
in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones.
Consequently, if user installs new kernels using e.g. update-manager,
the excessive kernels will not be removed by unattended-upgrade, and
eventually (small) /boot will become full.
Expected behavior: handle removing of unused packages differently at
least until other package management software installed by default can
handle removing of new unused packages.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: XFCE
Date: Sat Sep 17 11:28:44 2016
InstallationDate: Installed on 2016-09-05 (11 days ago)
InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions
More information about the foundations-bugs
mailing list