This bug was fixed in the package apt - 1.6.12
---------------
apt (1.6.12) bionic; urgency=medium
[ TilmanK ]
* Fix typo in German manpage translation
[ Michael Zhivich ]
* methods: https: handle requests for TLS re-handshake (LP: #1829861)
[ Julian Andres Klode ]
* Unlock dpkg locks in reverse locking order (LP: #1829860)
[ Simon Körner ]
* http: Fix Host header in proxied https connections (LP: #1838771)
[ Brian Murray ]
* Do not include squashfs file systems in df output. (LP: #1756595)
-- Julian Andres Klode <juli...@ubuntu.com> Tue, 03 Sep 2019 12:05:35
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829860
Title:
APT unlocks in same order as it locks
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
New
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Disco:
Fix Released
Bug description:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
[Test case]
Watch lock release with strace and see that it unlocks the right way.
[Regression potential]
Some other locking races or something?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+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
