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
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
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
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,
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
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
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
** 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.
** 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.
