[pkg-bacula-devel] Bug#825064: Bug#825064: Bacula director does not start silently due to database mismatch

[Klaus Ethgen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

Am Mo den 23. Mai 2016 um 21:19 schrieb Carsten Leonhardt:
> >> 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

Well, the documentation of dpkg-reconfigure states different:
   Da Sie bacula-director-sqlite3 neu konfigurieren, möchten Sie
   vielleicht auch die Datenbank, die es verwendet, neu installieren.

   Falls Sie die Datenbank für bacula-director-sqlite3 neu installieren
   wollen, sollten Sie diese Option wählen. Falls Sie dies nicht
   wünschen (falls Sie das Paket aus anderen Gründen neu konfigurieren),
   sollten Sie diese Option nicht wählen.

   Warnung: Falls Sie sich dazu entscheiden, die Datenbank neu unter
   einem bereits existierenden Namen zu installieren, wird die alte
   Datenbank ohne weitere Fragen entfernt. In diesem Fall wird unter
   /var/tmp/ eine Sicherungskopie der ursprünglichen Datenbank angelegt.

   Warnung: Falls Sie den Namen der Datenbank ändern wird die alte
   Datenbank nicht entfernt. Falls Sie den Namen des Benutzers ändern,
   der sich mit der Datenbank verbindet, werden die Rechte des
   ursprünglichen Benutzers nicht entfernt.

   Datenbank für bacula-director-sqlite3 neu installieren?

I read that in the way that the database will get lost.

Note that I have that database from before dbconfig was invented. And I
cannot risk that database to get lost. (True, I could recreate it from
existing tapes but this would be a pain in the a...)

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

That means that the parameter dbc_upgrade makes no sense at all? Upgrade
will be done if dbc_install is true otherwise not - ignoring the value
of dbc_upgrade..

> It wouldn't make any sense to reinstall the database on updates,
> especially without asking.

That is what I would say so.

> If you want, I'll ask the maintainer of dbconfig-common for help on this
> issue.

Well, My interpretation of that value(s) is:
dbc_install: Initially install a _new_ database
dbc_upgrade: Upgrade database(s)
dbc_remove: Remove existing databases at deinstallation

Double meaning of one parameter with driving another parameter useless
is not helpful.

> >> I'm closing this bug report, if you have further questions you can send
> >> them to pkg-bacula-devel at 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.

But this is the only question I get (see above).

Regards
   Klaus
- -- 
Klaus Ethgen                              http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen <Klaus at Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Charset: ISO-8859-1

iQGcBAEBCgAGBQJXQ2t/AAoJEKZ8CrGAGfasVnwL/jWuzMnqlkhaFpBWA/zKSygp
QEPGRXmcv5c7raGqpwROTYez25ZS/O/VMedCQ1qdCoOpeR+WGOddG2fFcui08Pm1
LLHCdR9YKio0Ti2Ign5zCwFtD7dYpXNAWUsvtvPWPoA07+F/MI/pqKWYciECxB69
ynjUOtYjJmrutEPLe9hRz9Wxz6w/SHQRWu0M2ADPipEigPqXIyzDA9lgKL5ogpaE
cdgB9y7f7rwZ2Mvt4a4Jpg6+DNzYUCHvcZsqDhGSyEzF+2va9He8xzlc0L1ZCU+B
SBi7pU0SXOtFlL2kFTvNWSdWBpZngttvmdlEOtWieOb3DlZYT89ORCEeu31U63aW
MW/2JJOeHgCsaWd3a9LFUBZ+ExfMyFrV8tcOqRhuEK/O6Avx65CtT2KeOxOBFNq7
duy/vT48+YUD6aQOHxDwQywZ865kO6ddFuoKspPu4yci/Lt0OiYhuN7vLNFIDUer
Tf+9h12wCnMlm5Gw8QRww11ADBcDszQoqiqjkZyMkQ==
=Ox39
-----END PGP SIGNATURE-----