This bug was fixed in the package apt - 1.2.29 --------------- apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts. Some post-invoke scripts install packages, which fails because the environment variable is not set. This sets the variable for all three kinds of scripts {pre,post-}invoke and pre-install-pkgs, but we will only allow post-invoke at a later time. (LP: #1796808) apt (1.2.28) xenial; urgency=medium [ Julian Andres Klode ] * apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159) * Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169) * Set DPKG_FRONTEND_LOCKED as needed when doing selection changes * http: Stop pipeline after close only if it was not filled before (LP: #1794957) * pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053) * Update libapt-pkg5.0 symbols for frontend locking [ David Kalnischkies ] * Support records larger than 32kb in 'apt show' (Closes: #905527) (LP: #1787120) -- Julian Andres Klode <juli...@ubuntu.com> Tue, 09 Oct 2018 12:35:03 +0200 ** Changed in: apt (Ubuntu Xenial) 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 https://bugs.launchpad.net/bugs/1796808 Title: frontend locking regression: dpkg::post-invoke scripts can't install packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Bug description: [Impact] The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered in DPkg::Pre-Install-Pkgs DPkg::Pre-Invoke DPkg::Post-Invoke To be run with the frontend lock held. This caused problems with some installer packages like libdvd-pkg which install a locally built package in such a hook. To reduce the impact, a fix has been applied in 1.7.0 which exports the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing dpkg to be run from those scripts. [Test case] Make sure that the test-frontend-lock test run by autopkgtest succeeds. This checks that: (1) the variable is correctly exported to those scripts (2) the frontend lock is still held (3) dpkg can be run from the post-invoke script [Regression potential] Depending on the script (for example, if the script starts a daemon manually or something like that), DPKG_FRONTEND_LOCKED might leak to other processes which might survive the apt call and thus revert surviving process to not using frontend locking. [Other info] This fix is for backwards compatibility only. Starting with the dd cycle, it will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially for post-invoke as well, if we find a better solution for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796808/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp