[can-not-install] prompt in postinst

Bug #93732 reported by Michael Vogt
74
This bug affects 9 people
Affects Status Importance Assigned to Milestone
blootbot (Debian)
Fix Released
Unknown
blootbot (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: blootbot

Found the following problem during a install test:

Setting up blootbot (1.2.0-5) ...
Creating sample /var/lib/blootbot/blootbot.users, you will need
to edit this and set a password before the bot is ready for use
See /usr/share/doc/blootbot/README.Debian for details

The bot will by default join the Freenode network, edit
/etc/blootbot/ircII.servers to change this
Creating a default config file as /etc/blootbot/blootbot.config
[ 1] Loaded config blootbot.config (47 items)
[ 2] Loading DB modules...
[ 3] MEM: (DBI // mysql) increased by 264 kB
[ 4] using MySQL support.
[ 5] Trying to see if we have already done this stuff...
[ 6] !WARN! PERL: DBI connect('blootbot:localhost','blootbot',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/blootbot/src/db_mysql.pl line 22
[ 7] !ERROR! cannot connect to localhost.
[ 8] !ERROR! since mysql is not available, shutting down bot!
[ 9] !WARN! PERL: Use of uninitialized value in join or string at /usr/share/blootbot/src/modules.pl line 379.
[ 10] !ERROR! UNKNOWN FUNCTION CALLED: main::closeSHM ()
[ 11] Could not connect to database blootbot, continuing
Please enter user information for root access to the mysql database.
The username is probably 'root', the password you should have set
yourself. If you haven't set one yet, leave it blank, and read
/usr/share/doc/mysql-server/README.Debian
Username:
Password:
[ 12] !ERROR! error: adminuser is blank.
blootbotsetup failed, rc == 1 at /var/lib/dpkg/info/blootbot.postinst line 87, <STDIN> line 5.
dpkg: error processing blootbot (--configure):
 subprocess post-installation script returned error exit status 25

It should use debconf for prompting and it should not fail if the adminuser is blank

Tags: packaging
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Confirmed in Gutsy.

Changed in blootbot:
status: Unconfirmed → Confirmed
Changed in blootbot:
assignee: nobody → dktrkranz
status: Confirmed → In Progress
Changed in blootbot:
assignee: dktrkranz → nobody
status: In Progress → Confirmed
Revision history for this message
Ralph Janke (txwikinger) wrote :

Confirmed in hardy

Changed in blootbot:
assignee: nobody → txwikinger
status: Confirmed → In Progress
Ralph Janke (txwikinger)
Changed in blootbot:
importance: Undecided → Low
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Ralph, are you actually working on fixing this? If not, I think it would make sense to unassign yourself from it so others don't hesitate to step up.

Thank you for your continued hard work on making Ubuntu even better.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

no response, I think it is better to leave the assignment open for anyone willing to work on this.

Changed in blootbot:
assignee: txwikinger → r0lf
assignee: r0lf → nobody
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This problem still exists in lucid.
I'm setting the status to confirmed since no one seems to be working on it.

Changed in blootbot (Ubuntu):
status: In Progress → Confirmed
Revision history for this message
Angel Abad (angelabad) wrote :

This problem still exists in oneiric.

Changed in blootbot (Ubuntu):
status: Confirmed → Triaged
Changed in blootbot (Debian):
status: Unknown → New
Changed in blootbot (Debian):
status: New → Fix Released
Revision history for this message
Vibhav Pant (vibhavp) wrote :

Sorry guys. I accidentally set this bug to the wrong status, could anybody revert it back to its original status??

Changed in blootbot (Ubuntu):
status: Triaged → Fix Released
Changed in blootbot (Debian):
status: Fix Released → New
Changed in blootbot (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.