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

[Luca Capello]

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

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.

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20120718/563e299a/attachment.pgp>