[debian-mysql] Bug#1109499: bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie

[Otto Kekäläinen]

Hi!

I skimmed through https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109499
quickly and my initial thought here is that Bacula (or any other program)
should not rely on dpkg maintainer scripts to upgrade the database as there
isn't any guarantees about what the initial state is, and if anything fails
it's really hard to restart or recover. Any failures happening during a
dpkg run in general will block the upgrades/installs/uninstalls for the
whole system as apt will refuse to do any new actions until the pending
dpkg package action has completed successfully.

Instead I would recommend to do the upgrade as part of the systemd/init
service startup sequence. If it fails it's much easier to restart and debug
and the failure will only affect one single service, not the whole OS
package management system. Doing an upgrade check and upgrading the
database as part of the startup sequence will also behave correctly if the
user is for example restoring an old database from backups and trying to
start it with a new version of Bacula.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20250731/86eab366/attachment.htm>