Package: fossology Version: 1.2.0-3.1 Followup-For: Bug #595593 Hi,
this also affects the piuparts test of fossology-agents:
Selecting previously unselected package fossology-agents.
(Reading database ... 14671 files and directories currently installed.)
Unpacking fossology-agents (from .../fossology-agents_1.2.0-3.1_amd64.deb) ...
Setting up fossology-agents (1.2.0-3.1) ...
*** Creating user and group ***
NOTE: group 'fossy' created
NOTE: user 'fossy' created
*** Making sure needed dirs exist with right ownership/permissions ***
NOTE: creating new /srv/fossology/repository/localhost directory
*** Checking database connectivity ***
ERROR: Unable to connect to the database
Connection string: 'dbname=fossology host=localhost user=fossy
password=fossy'
Connection status: '1'
ERROR: Failed to open database
ERROR: unable to connect to database, please check /etc/fossology/Db.conf
dpkg: error processing fossology-agents (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
fossology-agents
# cat /etc/fossology/Db.conf
dbname=fossology;
host=localhost;
user=fossy;
password=fossy;
The package does not give any clue what database it would like to use.
mysql? postgresql? oracle? There is not even a Suggests: any-db
I tested in a chroot, no db server installed on either host or chroot.
I also tried debconf priority low.
BTW, thats a great password ... (dbconfig-common comes into my mind ...)
Andreas
BTW, I'm currently trying piuparts tests that allow starting a database
server as that's a more sane environment to test packages requiring a
database.
fossology-agents_1.2.0-3.1.log.gz
Description: GNU Zip compressed data
