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

Paul Gevers elbrus at debian.org
Sun Jul 20 11:44:21 BST 2025


Hi,

On Sun, 20 Jul 2025 12:27:53 +0200 Niels Thykier <niels at thykier.net> wrote:
> Perharps debian-devel or other people that would be in similar 
> situations can help. Concretely, I suspect the postgres/mariaDB 
> maintainers would have been in a similar situation at some point (I 
> think PostgreSQL has a yearly bump of data base format). Personally, I 
> would probably reach out to the PostgreSQL maintainers / check the PG 
> packaging.

The situation for MariaDB warranted documentation in the Release Notes:

https://www.debian.org/releases/trixie/release-notes/issues.html#mariadb-major-version-upgrades-only-work-reliably-after-a-clean-shutdown

Maybe we can reduce the amount of people running into the scenario where 
this is needed by giving sound upgrade instructions?

Is the upgrade handled by dbconfig-common? I recall that will at least 
dump the database before trying the upgrade and notify the user of that 
in case of failures.

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20250720/98d72db1/attachment.sig>


More information about the pkg-bacula-devel mailing list