Packages in state successfully-tested but logfile contains failure to setup a database

Packages with failed logs because installation failed because no database could be connected. in oldstable222sid, 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!
2 - pass/bacula-director_13.0.4-4.log (piuparts.d.o) (tracker.d.o) (BTS) 1 - pass/bacula-server_13.0.4-4.log [all] (piuparts.d.o) (tracker.d.o) (BTS) 0 - pass/bacula_13.0.4-4.log [all] (piuparts.d.o) (tracker.d.o) (BTS) Affected packages in oldstable222sid: 3

Quality Assurance