2018-07-11 09:21:14 |
Julian Andres Klode |
bug |
|
|
added bug |
2018-07-11 09:21:20 |
Julian Andres Klode |
bug task added |
|
dpkg (Ubuntu) |
|
2018-07-11 09:33:22 |
Julian Andres Klode |
dpkg (Ubuntu): status |
New |
In Progress |
|
2018-07-11 09:33:24 |
Julian Andres Klode |
apt (Ubuntu): status |
New |
In Progress |
|
2018-08-22 09:54:16 |
Julian Andres Klode |
apt (Ubuntu): status |
In Progress |
Fix Released |
|
2018-08-22 09:54:19 |
Julian Andres Klode |
dpkg (Ubuntu): status |
In Progress |
Fix Released |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Bionic |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Bionic) |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
bug task added |
|
dpkg (Ubuntu Bionic) |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Xenial |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Xenial) |
|
2018-09-28 11:16:29 |
Julian Andres Klode |
bug task added |
|
dpkg (Ubuntu Xenial) |
|
2018-09-28 11:16:40 |
Julian Andres Klode |
apt (Ubuntu Xenial): status |
New |
Triaged |
|
2018-09-28 11:16:42 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
New |
Triaged |
|
2018-09-28 11:43:04 |
Julian Andres Klode |
description |
frontend locking fixes locking for dpkg frontends. Implementation is in dpkg git and apt support is coming soon. |
[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. |
|
2018-09-28 13:35:18 |
Julian Andres Klode |
apt (Ubuntu Xenial): status |
Triaged |
In Progress |
|
2018-09-28 13:35:19 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
Triaged |
In Progress |
|
2018-09-29 12:34:53 |
Francis Ginther |
tags |
|
id-5bae2d02f32c4e3b0a036f61 |
|
2018-10-01 13:49:44 |
Julian Andres Klode |
bug task deleted |
dpkg (Ubuntu) |
|
|
2018-10-01 17:12:24 |
Łukasz Zemczak |
apt (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2018-10-01 17:12:26 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2018-10-01 17:12:27 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
2018-10-01 17:12:30 |
Łukasz Zemczak |
tags |
id-5bae2d02f32c4e3b0a036f61 |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic |
|
2018-10-01 18:35:07 |
Łukasz Zemczak |
apt (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
2018-10-01 18:35:11 |
Łukasz Zemczak |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic verification-needed-xenial |
|
2018-10-04 07:13:31 |
Julian Andres Klode |
bug task deleted |
dpkg (Ubuntu Xenial) |
|
|
2018-10-04 07:13:36 |
Julian Andres Klode |
bug task deleted |
dpkg (Ubuntu Bionic) |
|
|
2018-10-04 07:13:39 |
Julian Andres Klode |
summary |
frontend locking |
apt frontend locking |
|
2018-10-04 12:19:10 |
Julian Andres Klode |
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. |
[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 |
|
2018-10-04 12:39:13 |
Julian Andres Klode |
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 |
[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 |
|
2018-10-05 07:30:07 |
Julian Andres Klode |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic verification-needed-xenial |
id-5bae2d02f32c4e3b0a036f61 verification-failed verification-failed-bionic verification-failed-xenial |
|
2018-10-17 22:26:14 |
Brian Murray |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-failed verification-failed-bionic verification-failed-xenial |
id-5bae2d02f32c4e3b0a036f61 verification-failed-bionic verification-needed verification-needed-xenial |
|
2018-10-17 22:34:17 |
Brian Murray |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-failed-bionic verification-needed verification-needed-xenial |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic verification-needed-xenial |
|
2018-10-18 13:19:36 |
Julian Andres Klode |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-needed verification-needed-bionic verification-needed-xenial |
id-5bae2d02f32c4e3b0a036f61 verification-done-bionic verification-needed verification-needed-xenial |
|
2018-10-18 13:27:08 |
Julian Andres Klode |
tags |
id-5bae2d02f32c4e3b0a036f61 verification-done-bionic verification-needed verification-needed-xenial |
id-5bae2d02f32c4e3b0a036f61 verification-done verification-done-bionic verification-done-xenial |
|
2018-10-25 15:20:52 |
Launchpad Janitor |
apt (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2018-10-25 15:21:04 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2018-10-25 15:29:32 |
Launchpad Janitor |
apt (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|