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 <rbal...@ubuntu.com> Thu, 01 Mar 2018 17:29:33 +0700
** Changed in: unattended-upgrades (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Bug description:
This may happen, if you boot one of the older kernels, that is not
protected by /etc/apt/apt.conf.d/01autoremove-kernels
Workaround: run
/etc/kernel/postinst.d/apt-auto-removal
during each boot (e.g. by using cron).
Note: The workaround breaks autoremoving feature of new unneeded kernels in
unattended-upgrades i.e. the setting
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set
in '/etc/apt/apt.conf.d/50unattended-upgrades'.
In shell:
$ uname -r
4.4.0-22-generic
$ apt-get -s autoremove
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Aug 21 16:11:27 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-28 (114 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
mtime.conffile..etc.kernel.postinst.d.apt-auto-removal:
2016-07-30T12:15:32.706300
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
