This bug was fixed in the package dbconfig-common - 1.8.40ubuntu1
---
dbconfig-common (1.8.40ubuntu1) jaunty-proposed; urgency=low
* dpkg/common: Fix for a location in the code where ucf was not being called
with the
now requiste --debconf-ok (LP: #384607)
-- Chuck Short
Accepted dbconfig-common into jaunty-proposed, the package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in advance!
** Changed in: dbconfig-common
I have reproduced the bacula installation error with dbconfig-common
from jaunty, 1.8.40, and can confirm that the version in jaunty-
proposed, 1.8.40ubuntu1, allows bacula to successfully complete
installation. I also installed and purged several other of dbconfig-
common's rdepends and ensured
** Attachment added: debdiff.diff
http://launchpadlibrarian.net/32157576/debdiff.diff
--
[SRU] bacula did not accept my password during installation
https://bugs.launchpad.net/bugs/384607
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Statement of Impact:
Users upgrading bacula from intrepid will get this wanring message:
bconfig-common: writing config to
/etc/dbconfig-common/bacula-director-mysql.conf
*** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok
