[pkg-bacula-devel] Bug#681790: Bug#681790: /usr/sbin/bacula-dir: fails to upgrade database when database is on a remote machine

[Alexander Golovko]

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:
>> Hi there!
>>
>> 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).

We should describe differences from upstream - dbconfig-common usage 
and common troubles.
It is something difficult for me, because english is not native for me, 
but i will try later.


>>
>> 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.

No, we should not use dpkg-reconfigure for change database parameters 
without database reinstallation.
If we run dpkg-reconfigure, dbconfig ask to reinstall database and 
rewrite config file
In choice of "don't reinstall database", dbconfig rewrite config file 
and add to it 'dbc_install=false', so this will stop future database 
upgrades.


> just to understand better (and avoid other useless bug reports):
> 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?

If you change only database connect parameters (host, dbname, user, 
password, etc), than you should not run dpkg-reconfigure, but should 
make changes in two places:
1. in bacula config
2. in dbconfig files 
(/etc/dbconfig-common/bacula-director-(mysql|pgsql|sqlite3).conf


>
> thank you
>>
>> Thx, bye,
>> Gismo / Luca
>
> _______________________________________________
> pkg-bacula-devel mailing list
> pkg-bacula-devel at lists.alioth.debian.org
> 
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bacula-devel

-- 
with best regards,
Alexander Golovko
email: alexandro at ankalagon.ru
xmpp: alexandro at ankalagon.ru