This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu14.1
---
aptdaemon (1.1.1+bzr982-0ubuntu14.1) xenial; urgency=medium
* Various locking fixes (LP: #1831981)
- Implement frontend locking (incl. fixup from 0ubuntu24)
- Adjust locking order to match APT
- U
This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu21.1
---
aptdaemon (1.1.1+bzr982-0ubuntu21.1) disco; urgency=medium
* Various locking fixes (LP: #1831981)
- Implement frontend locking (incl. fixup from 0ubuntu24)
- Adjust locking order to match APT
- Us
This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu19.1
---
aptdaemon (1.1.1+bzr982-0ubuntu19.1) bionic; urgency=medium
* Various locking fixes (LP: #1831981)
- Implement frontend locking (incl. fixup from 0ubuntu24)
- Adjust locking order to match APT
- U
Regarding the regression report on aptdaemon/armhf/xenial: aptdaemon
test suite hangs on arm* across all releases, but that's not new (it
hang occasionally before, or it just failed earlier, or in xenial's case
had the wrong depends and never ran).
It's working on all other releases, so it's unlik
disco - 1.1.1+bzr982-0ubuntu21.1 - was fine too
Skipping cosmic, as releasing this 9 days before EOL is pointless if not
potentially harmful.
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
** Tags removed: verification-need
Same procedure on bionic, with 1.1.1+bzr982-0ubuntu19.1 - same result :)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
xenial verified.
1. Installed aptdaemon 1.1.1+bzr982-0ubuntu14.1)
2. Ran python3 -c "import apt_pkg, time;
apt_pkg.FileLock('/var/lib/dpkg/lock-frontend').__enter__(); time.sleep(1000)"
3. Ran aptdcon --install xterm in other window
Result:
1. aptdcon waited while the Python 3 process was runnin
Hello Julian, or anyone else affected,
Accepted aptdaemon into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/aptdaemon/1.1.1+bzr982-0ubuntu14.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Julian, or anyone else affected,
Accepted aptdaemon into disco-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/aptdaemon/1.1.1+bzr982-0ubuntu21.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu23
---
aptdaemon (1.1.1+bzr982-0ubuntu23) eoan; urgency=medium
* Various locking fixes (LP: #1831981)
- Implement frontend locking
- Adjust locking order to match APT
- Use reverse order for unlocking
--
** Description changed:
[Impact]
- aptdaemon needs to implement frontend locking to avoid it stumbling over
clients that do implement it. We also change the locking order to lock in APT
order, and the unlock order becomes the reverse of that so that the behavior is
sane wrt other clients.
+ a
11 matches
Mail list logo