Package: bugzilla Version: 2.18-6 Severity: important Tags: sid After my workaround of Bug#303730 (manually renaming my database and user), upgrading from 2.18-3 to 2.18-6 I have to manually fix things which should have been detected, as shown below:
Preparing to replace bugzilla 2.18-3 (using .../dirson/bugzilla_2.18-6_all.deb) ... Unpacking replacement bugzilla ... dpkg: warning - unable to delete old file `/usr/share/bugzilla/web/data/template': Directory not empty dpkg: warning - unable to delete old file `/usr/share/bugzilla/web/data': Directory not empty Setting up bugzilla (2.18-6) ... Can't connect as user to the 'U04-bugzilla-STD' database ([EMAIL PROTECTED]:3306) Use dpkg-reconfigure bugzilla to change the settings. Cannot find answer file for checksetup.pl dpkg: error processing bugzilla (--install): subprocess post-installation script returned error exit status 3 Errors were encountered while processing: bugzilla And now : # dpkg-reconfigure bugzilla /usr/sbin/dpkg-reconfigure: bugzilla is broken or not fully installed # DEBIAN_PRIORITY=low /var/lib/dpkg/info/bugzilla.postinst configure Can't connect as user to the 'U04-bugzilla-STD' database ([EMAIL PROTECTED]:3306) Use dpkg-reconfigure bugzilla to change the settings. Cannot find answer file for checksetup.pl Now if I manually change bugzilla/mysql_user in the debconf database, "/var/lib/dpkg/info/bugzilla.postinst configure" and "dpkg --configure -a" succeed. Looks like the postinst correctly picked the database name from localconfig, but failed to pick the username for some reason. The problem is annoying in itself, but would have been mitigated if dpkg-reconfigure had been able to let me enter correct the db name - we cannot expect the average user will blissfully edit the debconf cache if anything went wrong :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
