Package: python-afl
Version: 0.5.4-1
Severity: normal
Building python-afl with sbuild in a chroot yields a hanging Python processes,
sometimes a single one, sometimes more:
<cut>
Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use
E: 10mount: umount:
/run/schroot/mount/unstable-amd64-sbuild-a9f92393-6906-43a7-86c5-68e30c747995/build:
target is busy
E: 10mount: (In some cases useful info about processes that
E: 10mount: use the device is found by lsof(8) or fuser(1).)
E: unstable-amd64-sbuild-a9f92393-6906-43a7-86c5-68e30c747995: Chroot setup
failed: stage=setup-stop
Chroot cleanup failed
{...}
$ lsof
/run/schroot/mount/unstable-amd64-sbuild-a9f92393-6906-43a7-86c5-68e30c747995
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python2.7 16613 aham rtd DIR 0,42 4096 2737263
/run/schroot/mount/unstable-amd64-sbuild-a9f92393-6906-43a7-86c5-68e30c747995
python2.7 16753 aham rtd DIR 0,42 4096 2737263
/run/schroot/mount/unstable-amd64-sbuild-a9f92393-6906-43a7-86c5-68e30c747995
</cut>
I've experienced this with earlier package versions, too. I couldn't nail it
down so far,
would guess this isn't reproducible everywhere.
DS
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-afl depends on:
ii afl 2.28b-1
ii libc6 2.23-4
ii python 2.7.11-2
pn python:any <none>
python-afl recommends no packages.
python-afl suggests no packages.
-- no debconf information
