Here's how I see it happening, someone who understands this better can
correct my reasoning:
in file:
/usr/share/bugzilla/debian/postinst-db.pl
it says:
...
# according to installation way user choosed,
# we'll do different things.
my $install_way;
my $default_file = '/etc/mysql/debian.cnf';
...
and
...
# The Automatic way will read /etc/mysql/default.cnf
# and will use the values found there.
if ($install_way eq 'Automatic') {
# At this time, Debian MySQL user must be available.
init_default_vars();
debug "Debian MySQL maintainer is : $DEBIAN_DBUSER";
# At this time, we have to set the good values
# for accessing the MySQL database.
$mysql_host = $BUGZILLA_DBHOST;
$mysql_port = $BUGZILLA_DBPORT;
$mysql_name = $BUGZILLA_DBNAME;
$mysql_name_escaped = $mysql_name;
$mysql_user = $BUGZILLA_DBUSER;
$mysql_user_pwd = $BUGZILLA_DBPASS;
$mysql_need_root = 'true';
$mysql_root_name = $DEBIAN_DBUSER;
$mysql_root_pwd = $DEBIAN_DBPASS;
...
which to me seems to indicate choosing user 'debian-sys-maint' as the
$mysql_root_name, contrary to the changelog entry (which is a bit short,
I must admit).
After granting all privileges to user 'debian-sys-maint' and trying
"sudo aptitude reinstall bugzilla" the installation procedure says:
[EMAIL PROTECTED]:~$ sudo aptitude reinstall bugzilla
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages will be REINSTALLED:
bugzilla
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Setting up bugzilla (2.20-1) ...
Database bugzilla already exists, skipping database creation.
...at which point it stays probably until the end of time. Some 15
minutes later I got this pop-up box in the bottom right corner of my
desktop saying "partition / is 95% full", which caused me to panic and
hit ctrl+c in the terminal that was reinstalling bugzilla, because that
partition had 7.9GB of free space before reinstalling. I was afraid the
/ partition would fill up, which wouldn't be nice...
After reading more stuff in the 'net I cannot be sure whether this was a
desired effect. It sounds a bit stunning that it would eat up that much
disk space, but I'll let that one pass, and study more about the
package.
--
Bugzilla installation fails to create a database
https://launchpad.net/bugs/55747
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
