Hi Klaus, >> I've tested an update from 7.0.5, with dbc_install='false' in >> /etc/dbconfig-common/bacula-director-sqlite3.conf. This time the update >> wasn't applied, apparently dbconfig-common doesn't apply any changes >> when this is set. >> >> Please change it back to 'true' and run "dpkg-reconfigure >> bacula-director-sqlite3" if you want automatic updates in the future. > > As the description states, with that dbc_install set to true would > overwrite the database completely with the next upgrade. > > That would be even more fatal as all other solutions as that would mean > to forgot all about previous backups and locations.
it doesn't delete the database on upgrades. This is the description, taken from /etc/dbconfig-common/bacula-director-sqlite3.conf: # dbc_install: configure database with dbconfig-common? # set to anything but "true" to opt out of assistance Admittedly, the documentation of that variable is a bit lacking, but if this is 'false', dbconfig-common will not touch the database in any case. See also: https://lists.debian.org/debian-mentors/2010/04/msg00200.html It wouldn't make any sense to reinstall the database on updates, especially without asking. If you want, I'll ask the maintainer of dbconfig-common for help on this issue. >> I'm closing this bug report, if you have further questions you can send >> them to pkg-bacula-de...@lists.alioth.debian.org > > I don't think, that it should be closed. dbc_install is about installing > a new, empty database with every upgrade and dbc_upgrade is about > upgrading a existing one. > > Nobody would, I believe, vote for dbc_install at all except for the > initial installation of the package. Otherwise it is the most dangerous > operation ever. The dangerous operation would be to "dpkg-reconfigure bacula-director-sqlite3" and then answer "yes" to the question of you want to reinstall the database. Yours, Carsten