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-14 09:14 UTC
Packages with failed logs because installation failed because no database could be connected. in oldstable22testing, sorted by reverse dependency count.

Just how buggy these packages really are is discussed in #595652 at the moment.

The commandline to find these logs is:

COMMAND='grep -E "(warning: database package not installed|dbconfig-common: .* configure: (aborted|noninteractive fail|ignoring errors from here forwards)|updating database schema for .*...command failed with code 0|(postgres|psql): could not connect to server: No such file or directory|DBI connect.* failed: could not connect to server|pg_pconnect\(\): Unable to connect to PostgreSQL server|Non-default port in /etc/postgresql/.*/main/postgresql.conf|Unable to connect to MySQL server|unable to connect to mysql server)"'

Please file bugs!

Affected packages in oldstable22testing: 14