[Expired for dbconfig-common (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: dbconfig-common (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubun
Can you please explain why this is considered a bug? If the database is
corrupt (or at least, the operator configured the package to use a wrong
database) isn't this "expected" behavior?
Relevant part of the DpkgTerminalLog.gz:
Creating config file /etc/dbconfig-common/bacula-director-mysql.conf w
** Changed in: dbconfig-common (Ubuntu)
Importance: Undecided => Low
** Changed in: dbconfig-common (Ubuntu)
Status: New => Confirmed
--
package bacula-director upgrade failed because it couldn't connect to
mysql-server
https://bugs.launchpad.net/bugs/569313
You received this bug noti
** Package changed: bacula (Ubuntu) => dbconfig-common (Ubuntu)
--
package bacula-director upgrade failed because it couldn't connect to
mysql-server
https://bugs.launchpad.net/bugs/569313
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to d
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/45145347/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45145348/Dependencies.txt
** Attachment added: "Df.txt"
http://launchpadlibrarian.net/45145349/Df.txt
** Attachment added:
