This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 in a few hours, and then
in the -proposed repository.
Please help us by
Tested with 1.1ubuntu1.18.04.7~16.04.1:
$ sudo chroot x-test-1803749/
root@MacBookAir-test:/# apt install unattended-upgrades zsh
Reading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
iso-codes python-apt-common python3-apt xz-utils
** Changed in: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Cosmic)
Importance: Undecided => High
--
You received this bug notification
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then
in the -proposed repository.
Please help us by
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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/1803749
Title:
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7
---
unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium
* Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
Performing upgrades in service's ExecStop did not work when the
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.0
---
unattended-upgrades (1.5ubuntu3.18.10.0) cosmic; urgency=medium
* Revert to running unattended-upgrades.service in multi-user.target
* Trigger unattended-upgrade-shutdown actions with
Verified unattended-upgrades 1.5ubuntu3.18.10.0 on cosmic:
...
left to upgrade set()
All upgrades installed
InstCount=0 DelCount=0 BrokenCount=0
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2018-11-27
21:13:31
root@yogi:/# apt autoremove
Reading
Verified 1.1ubuntu1.18.04.7 on bionic:
...
left to upgrade set()
All upgrades installed
InstCount=0 DelCount=0 BrokenCount=0
root@yogi:/# apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
zsh
** Description changed:
[Impact]
- * Originally autoremovable packages can be removed as newly autoremovable
ones by unattended-upgrades
- * This can surprise users potentially removing packages which are needed for
the system's operation.
+ * Originally autoremovable packages can be
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.5ubuntu3.18.10.0 in a few hours, and then in the
-proposed repository.
Please help us by testing
This bug was fixed in the package unattended-upgrades - 1.8
---
unattended-upgrades (1.8) unstable; urgency=medium
* Add note about increasing InhibitDelayMaxSec for InstallOnShutdown to
50unattended-upgrades.
* Ship historical md5sums of
** Description changed:
+ [Impact]
+
+ * Originally autoremovable packages can be removed as newly autoremovable
ones by unattended-upgrades
+ * This can surprise users potentially removing packages which are needed for
the system's operation.
+
+ [Test Case]
+
+ * WIP, see Original Bug
I'm fixing the issue here in u-u:
https://github.com/mvo5/unattended-upgrades/pull/156
However I believe ActionGroup may need at least better documentation to
clearly state when ActionGroups should be reset.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => In Progress
**
This is caused by unattended-upgrades having an ActionGroup during the
clear. So, UnattendedUpgrades cache should likely overwrite clear() and
make it reset the action group, for example (after making actiongroup
global):
def clear(self):
global actiongroup
actiongroup.release() #
17 matches
Mail list logo
