Package: fusionforge-plugin-scmgit,fusionforge-plugin-scmsvn Version: 6.0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package left processes running after the package has been removed and/or purged. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. In https://lists.debian.org/debian-devel/2009/08/msg00182.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): 1m42.8s ERROR: FAIL: Processes are running inside chroot: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME xinetd 6292 root cwd DIR 0,20 460 3378999138 /tmp/piupartss/tmpwjdP5B xinetd 6292 root rtd DIR 0,20 460 3378999138 /tmp/piupartss/tmpwjdP5B xinetd 6292 root mem REG 0,20 43592 3379009778 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libnss_nis-2.19.so xinetd 6292 root mem REG 0,20 31632 3379009766 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libnss_compat-2.19.so xinetd 6292 root mem REG 0,20 47712 3379009772 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libnss_files-2.19.so xinetd 6292 root mem REG 0,20 1729984 3379009770 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libc-2.19.so xinetd 6292 root mem REG 0,20 35176 3379009767 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libcrypt-2.19.so xinetd 6292 root mem REG 0,20 1051056 3379009781 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libm-2.19.so xinetd 6292 root mem REG 0,20 89104 3379009768 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/libnsl-2.19.so xinetd 6292 root mem REG 0,20 140928 3379009775 /tmp/piupartss/tmpwjdP5B/lib/x86_64-linux-gnu/ld-2.19.so xinetd 6292 root 0r CHR 1,3 0t0 3379007767 /tmp/piupartss/tmpwjdP5B/dev/null xinetd 6292 root 1r CHR 1,3 0t0 3379007767 /tmp/piupartss/tmpwjdP5B/dev/null xinetd 6292 root 2r CHR 1,3 0t0 3379007767 /tmp/piupartss/tmpwjdP5B/dev/null cheers, Andreas
fusionforge-plugin-scmgit_6.0.3-1.log.gz
Description: application/gzip
