Hi Enrico! On Wed, 18 Jul 2012 18:35:07 +0200, AZ Imballaggi S.r.l. - Enrico Ghera wrote: > Il 18/07/2012 18:03, Luca Capello ha scritto: >> On Wed, 18 Jul 2012 03:18:44 +0200, Alexander Golovko wrote: >>> So, this is not a bug in package, but dbconfig-common habits. >>> Ofcourse, we should describe database upgrade habits in README.Debian >>> UPGRADE section. >> If you want to do that, then please go ahead, but strictly speaking this >> is not something that belongs to Debian, but in upstream manual. Debian >> provides a way to manage local and remote database, via dbconfig-common. >> If the admin changes that, than she/he should *know* that automatic >> upgrades could fail (Debian can not assure all possible configurations). >> >> Enrico, I am sorry for the bug, but I bet that having configured the >> remote database via dbconfig-common (thus via `dpkg-reconfigure >> bacula-director-mysql`) would have resulted in a correct upgrade. > just to understand better (and avoid other useless bug reports):
FTR, no bug report is useless IMHO: this one actually let you know how the Bacula database configuration is managed. > everytime I modify my database settings I should run dpkg-reconfigure? > doing the work twice? (one for actual conf and one for dbconfig) > or I should run dpkg-reconfigure and it updates my conf as well? > or my brain is dead and I have not understood anything? The second option: since the database configuration is managed, centrally, by dbconfig-common, you should not touch it by hand, but with dpkg-reconfigure. Doing this should update: 1) /etc/dbconfig-common/bacula-director-mysql.conf 2) all the relevant files in /etc/bacula/ Feel free to ask for more, if needed :-) Thx, bye, Gismo / Luca
pgpnMrr8rXEaQ.pgp
Description: PGP signature
