This bug was fixed in the package apt - 1.8.3

apt (1.8.3) unstable; urgency=medium

  [ 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)

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 <>  Fri, 09 Aug 2019 11:16:15

** Changed in: apt (Ubuntu Disco)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  APT unlocks in same order as it locks

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  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:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to