General information
About
News
FAQ
Contact us
Documentation
How to file bugs
using templates
Debian policy
piuparts.d.o configuration:
piuparts.conf,
distros.conf,
scripts and logs
README
README_server
piuparts manpage
Summaries
Bugs filed
Suites overview
Suite: oldstable22testing
by maintainer / uploader
by source package
states graph
all tested suites
experimental
sid2experimental
sid
sid-strict
sid-nodoc
sid-merged-usr
sid-broken-symlinks
testing2sid
forky
forky-rcmd
trixie
trixie-rcmd
trixie-security
trixie-pu
trixie2next
bookworm
bookworm-rcmd
bookworm-security
bookworm-pu
bookworm2next
bullseye
bullseye-rcmd
bullseye-security
bullseye-pu
bullseye2next
stable2sid
stable22sid
oldstable222sid
oldstable22testing
src: piuparts
Source
piuparts.d.o bugs
piuparts bugs / ToDo
Other Debian QA efforts
Debian QA Group
Dose tools (former: EDOS)
Lintian
Debian Package Tracker
Ultimate Debian Database
jenkins.debian.net
ci.debian.net
Last update
2025-09-09 09:13 UTC
Packages with failed logs because of processes left behind in oldstable22testing, sorted by reverse dependency count.

There were processes running inside the chroot at the end of the piuparts run. This is probably due to directly calling /etc/rc.d/ scripts in packages maintainer scripts, which is a violation of policy 9.3.3.2 and must be replaced by using invoke-rc.d (which will respect an optionally existing policy-rc.d) - see https://www.debian.org/doc/debian-policy/ch-opersys.html#interfacing-with-init-systems, /usr/share/doc/sysv-rc/README.invoke-rc.d.gz and /usr/share/doc/sysv-rc/README.policy-rc.d.gz.

According to the thread started at 200908061127.35727.holger@layer-acht.org these bugs are to be filed with severity serious.

The commandline to find these logs is: 

COMMAND='grep -E "ERROR: FAIL: Processes are running inside chroot"'

Please file bugs!

Affected packages in oldstable22testing: 1