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

[Sven Hartge]

On 20.07.25 12:44, Paul Gevers wrote:
> 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.

I am inclined to just switch the default to true, so automated upgrade 
will work, I have prepared a branch for this.

Carsten will need to weigh in though.

I also intent to an addition to the release-notes documenting the need 
for enough space to be available for the upgrade to work.

Grüße,
Sven.