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 Bionic)
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/1698159
Title:
linux-cloud-tools version specific packages are being removed by
unattended-upgrade's Remove-Unused-Dependencies
Status in apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Committed
Status in unattended-upgrades source package in Bionic:
Fix Released
Bug description:
When running kernel version 4.4.0-78 (for example) and the unattended-
upgrade packages installs a new kernel 4.4.0-79 (for example) the
linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
packages are removed by the Remove-Unused-Dependencies rule, because
unlike "normal" kernel packages they are not excluded by
/etc/apt/apt.conf.d/01autoremove-kernels.
The linux-cloud-tools package has the hyper-v integration services
daemons in it, so it's deletion leaves some of the integration not
working.
Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
hyper-v users aren't caught out by this?
Thanks,
Ian.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 15 15:27:35 2017
InstallationDate: Installed on 2016-04-25 (415 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.3)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.640000
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+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
