dbconfig-common cannot create database for package

Bug #113310 reported by neutrico
12
Affects Status Importance Assigned to Milestone
dbconfig-common (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Edgy by neutrico
Nominated for Feisty by neutrico
Nominated for Gutsy by neutrico

Bug Description

Binary package hint: dbconfig-common

Dbconfig-common fails to create mysql user for package.

Bug is in file: /usr/share/dbconfig-common/internal/mysql

line 271 "_dbc_nodb="yes" dbc_mysql_exec_file "$l_sqlfile" is not executed and first dbconfig-common doesn't create mysql user for package and in consequence cannot create empty database for package (because database is created by mysql user defined from package not by mysql root)

So, what we can see at the end is error message that dabatase for example "cacti" doesn't exist so, dbconfig common cannot configure package properly.

As a workaround user can just create empty database for package. But it's not acceptable because requires unecessary user interaction, and also user has to know what database name is required for package. (In some cases database name is different than package name).

This bug is pretty important because affects all packages that depends on dbconfig-common.

Tags: packaging
Revision history for this message
chantra (chantra) wrote :

Confirn=ming as bug#70938 was already confirmed

Changed in dbconfig-common:
status: Unconfirmed → Confirmed
Daniel T Chen (crimsun)
Changed in dbconfig-common:
importance: Undecided → Medium
status: Confirmed → Fix Released
Revision history for this message
neutrico (neutrico) wrote :

This "fix-released" is not 100% true. Because fix is available as upstream upgrade to 1.8.34. And package in this version is available in Gutsy but not in Feisty or Edgy.
Please release upgrade for Feisty and Edgy especially because this but affects other packages that depends on dbconfig-common (such as cacti and other).

Revision history for this message
chantra (chantra) wrote :

I have just installed cacti on debian etch and the database was created without issue. So it is fixed on debian stable.

current debian version:
1.8.29+etch1

Revision history for this message
neutrico (neutrico) wrote :

This bug wasn't a bug in debian. In debian dbconfig-common works properly (version 1.8.29, 1.8.30 etc...). This bug affects ubuntu because ubuntu has some different shell (sh/bash/dash) settings.

Debian changelog for 1.8.33 says: " * include a long-neglected fix from Adam Lebsack, which seems to fix the
     problems prevents dbconfig-common from working with dash (closes: #406127).
     this was also likely the cause of dbconfig appearing to attempt creating
     the database/user in the wrong order (closes: #418479)." And this is also fix for bug in ubuntu.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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