General information
About + News
Overview
FAQ
Source
piuparts.d.o bugs
piuparts bugs / ToDo
Contact us
Documentation
piuparts manpage
README
README_server
piuparts.d.o configuration:
piuparts.conf,
distros.conf
and scripts
How to file bugs
Debian policy
Available reports
Bugs filed
experimental
sid2experimental
sid
sid-strict
sid-nodoc
testing2sid
stable2sid
stable22sid
buster
buster-rcmd
stretch2buster
stretch2buster-rcmd
stretch2bpo2buster
stretch2bpo
stretch
stretch-rcmd
stretch-security
stretch-pu
stretch2proposed
oldstable222sid
oldstable22testing
jessie2stretch
jessie2Xstretch
jessie2stretch-rcmd
jessie2Xstretch-rcmd
jessie2bpo2stretch
jessie2bpo
jessie
jessie-rcmd
jessie-security
jessie-pu
jessie2proposed
wheezy2jessie
wheezy2jessie-rcmd
wheezy2bpo2jessie
wheezy2lts
wheezy
wheezy-security
wheezy-pu
squeeze2wheezy-lts
squeeze2wheezy
squeeze2bpo-sloppy
squeeze2bpo2wheezy
squeeze2squeeze-lts
squeeze
lenny2squeeze
by maintainer / uploader
by source package
Other Debian QA efforts
Debian QA Group
Dose tools (former: EDOS)
Lintian
Debian Package Tracker (former: PTS)
Ultimate Debian Database
jenkins.debian.net
ci.debian.net
Last update
2017-10-19 12:37 UTC
Packages with failed logs with the string "command not found" in sid-strict, sorted by reverse dependency count.

From the third paragraph about the meaning of the depends field in https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps

The Depends field should also be used if the postinst, prerm or postrm scripts
require the package to be present in order to run. __Note, however, that the
postrm cannot rely on any non-essential packages to be present during the
purge phase__.

NOTE: it has not been verified that this error really caused the package to fail the piuparts test, but it did fail.
There are also successful logs with "command not found" (though not listed below).

The commandline to find these logs is:

COMMAND='grep -E "command not found|: not found"'

Please file bugs!

Affected packages in sid-strict: 7