[Touch-packages] [Bug 1781169] Re: apt frontend locking
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 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 Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
apt frontend locking
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
Bug description:
[Impact]
apt acquires /var/lib/dpkg/lock but has to release it while running dpkg,
offering a short window for other clients to acquire the lock. This implements
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by
apt for dpkg to run.
dpkg will try to acquire the frontend lock as well, unless told not to
do so via an environment variable, which apt does; hence concurrent
runs of dpkg without other locking can't happen.
[Test case]
Run strace apt install $something and check that lock-frontend is acquired at
the beginning and not released until the end.
[Regression potential]
Frontend locking failures are in English, as there are no translations yet.
More locks also mean more potential for locking to go wrong across programs,
but since we don't have any waiting locks we at least won't deadlock.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; 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.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* 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
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+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/1781169
Title:
apt frontend locking
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
Bug description:
[Impact]
apt acquires /var/lib/dpkg/lock but has to release it while running dpkg,
offering a short window for other clients to acquire the lock. This implements
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by
apt for dpkg to run.
dpkg will try to acquire the frontend lock as well, unless told not to
do so via an environment variable, which apt does; hence concurrent
runs of dpkg without other locking can't happen.
[Test case]
Run strace apt install $something and check that lock-frontend is acquired at
the beginning and not released until the end.
[Regression potential]
Frontend locking failures are in English, as there are no translations yet.
More locks also mean more potential for locking to go wrong across programs,
but since we don't have any waiting locks we at least won't deadlock.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
Same with 1.2.29 from xenial:
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
[...] reading files ]
close(5)= 0
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(37, F_SETFD, FD_CLOEXEC) = 0
close(5)= 0
fcntl(37, F_GETFL) = 0x1 (flags O_WRONLY)
close(37) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3741, si_uid=0,
si_status=0, si_utime=0, si_stime=0} ---
[ reading files and writing extended_states stuff; no close(4) ]
close(4)= 0
close(5)= -1 EBADF (Bad file descriptor)
close(3)= 0
+++ exited with 0 +++
** 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 seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
apt frontend locking
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
apt acquires /var/lib/dpkg/lock but has to release it while running dpkg,
offering a short window for other clients to acquire the lock. This implements
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by
apt for dpkg to run.
dpkg will try to acquire the frontend lock as well, unless told not to
do so via an environment variable, which apt does; hence concurrent
runs of dpkg without other locking can't happen.
[Test case]
Run strace apt install $something and check that lock-frontend is acquired at
the beginning and not released until the end.
[Regression potential]
Frontend locking failures are in English, as there are no translations yet.
More locks also mean more potential for locking to go wrong across programs,
but since we don't have any waiting locks we at least won't deadlock.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
apt 1.6.6 from bionic: I verified that lock-frontend was opened and
locked at the beginning, that lock was locked after it, lock released
before dpkg is called, and that lock-frontend was not released until the
end.
[...]
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
[ ... Reading files ... ]
close(5)= 0
[... running dpkg and rebuilding cache; no close(4) ]
close(4)= 0
close(5)= -1 EBADF (Bad file descriptor)
close(3)= 0
+++ exited with 0 +++
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1781169
Title:
apt frontend locking
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
apt acquires /var/lib/dpkg/lock but has to release it while running dpkg,
offering a short window for other clients to acquire the lock. This implements
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by
apt for dpkg to run.
dpkg will try to acquire the frontend lock as well, unless told not to
do so via an environment variable, which apt does; hence concurrent
runs of dpkg without other locking can't happen.
[Test case]
Run strace apt install $something and check that lock-frontend is acquired at
the beginning and not released until the end.
[Regression potential]
Frontend locking failures are in English, as there are no translations yet.
More locks also mean more potential for locking to go wrong across programs,
but since we don't have any waiting locks we at least won't deadlock.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed verification-failed-xenial ** Tags added: verification-needed verification-needed-xenial -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
Frontend locking causes a regression: dpkg::post-invoke and other related scripts can no longer install/remove packages, as they are now called with 'lock' released, but 'lock-frontend' not. This needs a further change to set DPKG_FRONTEND_LOCKED for those scripts when the frontend lock is acquired. ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-failed verification-failed-bionic verification-failed-xenial -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
** Description changed: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - - unattended-upgrades + - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
[Touch-packages] [Bug 1781169] Re: apt frontend locking
** Description changed: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. + + [Other info] + This is part of a wider series of SRUs for frontend locking + + - dpkg (bug 1796081) + - apt (bug 1781169) + - python-apt (bug 1795407) + - packagekit (bug 1795614) + - unattended-upgrades + - aptdaemon (no bug filed yet) + + Further details about frontend locking can be found in + https://lists.debian.org/debian-dpkg/2017/01/msg00044.html -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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
