This bug was fixed in the package apt - 1.8.2+19.10
---------------
apt (1.8.2+19.10) eoan; urgency=medium
* Upload to eoan
apt (1.8.2) unstable; urgency=medium
[ Alwin Henseler ]
* Flip /: in documented default value of DPkg::Path (Closes: #917986)
[ TilmanK ]
* Fix typo in German manpage translation
[ Américo Monteiro ]
* Portuguese manpages translation update (Closes: #926614)
[ Jean-Pierre Giraud ]
* French manpages translation update (Closes: #929290)
[ Michael Zhivich ]
* methods: https: handle requests for TLS re-handshake (LP: #1829861)
[ Julian Andres Klode ]
* Unlock dpkg locks in reverse locking order (LP: #1829860)
-- Julian Andres Klode <juli...@ubuntu.com> Tue, 28 May 2019 23:25:22
+0200
** Changed in: apt (Ubuntu)
Status: New => 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
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]
...
[Regression potential]
...
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
