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 to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh!
The fix has been applied in the upstream source and has been fixed for Karmic. You can look at the fix at:
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
old- style, non-debconf prompting. Ugh!
*** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
and pass it this parameter. For now, ucf will revert to using
The fix has been applied in the upstream source and has been fixed for Karmic. You can look at the fix at:
http:// git.debian. org/?p= dbconfig- common/ dbconfig- common. git;a=commit; h=eff8932fbc628 9526ece2a7a38c6 0e4c8ab3f259
I have attached the debdiff which fixes this problem in Karmic.
How to Reproduce:
1. Install bacula from intrepid.
2. Upgrade to Jaunty.
The fix is a one liner and there should be no impact.
If you have any questions please let me know.
Regards
chuck