This bug was fixed in the package python-apt -
1.1.0~beta1ubuntu0.16.04.4
---
python-apt (1.1.0~beta1ubuntu0.16.04.4) xenial; urgency=medium
* apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870)
* apt.Cache: Use explicit, more safe locking in update()
*
without SystemLock being held works fine:
root@xx:~# strace -o $PWD/log -e openat,open,close,fcntl python3 $PWD/foo.py
(Reading database ... 25835 files and directories currently installed.)
This was for xenial 1.1.0~beta1ubuntu0.16.04.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package
Hello Julian, or anyone else affected,
Accepted python-apt into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.1.0~beta1ubuntu0.16.04.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Bug watch removed: Debian Bug tracker #922416
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Tracking the regression in bug 1826870
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package in
@sil2100 I think there is a regression in the other locking fixes, as
reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 -
but that said, we have that in every other release too, and I'll upload
SRUs for that later.
** Bug watch added: Debian Bug tracker #922416
@juliank is this upload still relevant and good for release? Last time
it was 'blocked' on the unattended-upgrades SRU - and that one has
landed in xenial-updates already. Can we release it now, or does it need
a re-upload?
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as
Got it. Thanks for the info.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package in Ubuntu:
Fix
We don't plan to. Trusty does not run unattended-upgrades by default, so
there's no strong need for frontend locking in there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Hello! Is there any change this fix will be backported to ubuntu/trusty?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
This bug was fixed in the package python-apt - 1.6.3
---
python-apt (1.6.3) bionic; urgency=medium
* Frontend locking and related locking improvements (LP: #1795407)
- apt.Cache: Keep / Re-establish the system lock in commit()
- apt.Cache: Keep archive locked during
Same for xenial (1.1.0~beta1ubuntu0.16.04.3).
Also, strace logs look like this, in case we want to see how we can be
sure it's kept locked all the time:
[...]
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 39
fcntl(39, F_SETFD, FD_CLOEXEC) = 0
fcntl(39, F_SETLK,
FTR, with the locking with statement, without the SRU, it fails, as
expected (both in bionic and xenial), e.g.:
dpkg: error: dpkg status database is locked by another process
E:Sub-process /usr/bin/dpkg returned an error code (2)
Traceback (most recent call last):
File
bionic 1.6.3:
1. Verified that the lock is hold during dpkg run added lslocks to
aptitude prerm:
$ lxc exec bbb -- strace -o $PWD/log -e openat,open,close,fcntl python3
$PWD/foo.py
(Reading database ... 28970 files and directories currently installed.)
Removing aptitude (0.8.10-6ubuntu1) ...
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as
** Tags added: id-5bae2d1cfc953731f10adda4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package in
Hello Julian, or anyone else affected,
Accepted python-apt into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.1.0~beta1ubuntu0.16.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Julian, or anyone else affected,
Accepted python-apt into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-apt/1.6.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: python-apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: python-apt (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in
** Description changed:
[Impact]
- foo
+ Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
+
+ (1) The archives lock was only taken for a short time, when it should
+ have been kept for the duration of an installation,
24 matches
Mail list logo
