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
As the log shows I actually tested with 1.1ubuntu1.18.04.7~16.04.1, the
correct version.
** 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
Touch
Tested 1.1ubuntu1.18.04.7~16.04.1:
Previous version:
root@x-uu-1789637-2:~# strace unattended-upgrade --verbose --dry-run 2>&1 |
grep lock
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
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
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.6
---
unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium
* Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is
available. Also stop running when reacquiring the lock
Tested with 1.1ubuntu1.18.04.6:
root@uu-frontend-lock:~# strace unattended-upgrade --verbose --dry-run 2>&1 |
grep lock
openat(AT_FDCWD, "/var/run/unattended-upgrades.lock",
O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
0640) =
It wasn't clear from this bug report whether or not this is fixed in
Cosmic but I did some detective work and yes it is, setting it to Fix
Released.
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: unattended-upgrades (Ubuntu Bionic)
** Description changed:
[Impact]
Apt and dpkg implemented the Frontend Locking API and unattended-
upgrades needs to adopt it to not leave the packaging system unlocked
while passing control to python-apt and dpkg to perform package
installations and removals. Leaving the packaging
** Description changed:
- Frontend lock support for apt and dpkg is tracked in LP: #1781169, this
- bug tracks unattended-upgrades changes
+ [Impact]
+
+ Apt and dpkg implemented the Frontend Locking API and unattended-
+ upgrades needs to adopt it to not leave the packaging system unlocked
+
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
12 matches
Mail list logo
