Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like:
"umount: /tmp/tmptmucmfm0/target/dev: target is busy"
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout).
Hi,
while testing I found that when running apt feature related to add-apt-repository like:
apt: yourppa"
sources:
ignored1:
source: "ppa:paelzer/
Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like: 0/target/ dev: target is busy"
"umount: /tmp/tmptmucmfm
Here an excerpt from a lsof +fg afterwards. 0/target/ dev/urandom 0/target/ dev/null 0/target/ dev/null 0/target/ dev/null 0/target/ dev/null
dirmngr 6771 root 1r CHR LG,0x80000 1,9 0t0 11 /tmp/tmptmucmfm
dirmngr 6771 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm
gpg-agent 6776 root 0r CHR LG 1,3 0t0 6 /tmp/tmptmucmfm
gpg-agent 6776 root 1w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm
gpg-agent 6776 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout).