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: bookworm
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-11 06:08 UTC
Packages with failed logs because of not enough force in bookworm, sorted by reverse dependency count.

The piuparts logfile for these packages contains the string

E: There are problems and -y was used without --force-yes
, which is usually an indication, that an essential package needs to be removed to install this package. As piuparts does not use that much force, the piuparts test fails.

This is usually not an error in the package and it needs to be seen how piuparts should deal with it.

The commandline to find these logs is:

COMMAND='grep -E "E: There are problems and -y was used without --force-yes|E: Essential packages were removed and -y was used without --allow-remove-essential"'

Please file bugs!

Affected packages in bookworm: 1