[pkg-bacula-devel] Piuparts / Upgrade confirmation

[Sven Hartge]

On 22.06.24 13:27, Carsten Leonhardt wrote:
> Sven Hartge <sven at svenhartge.de> writes:

> I've put the question in bacula-common, it's the basis for everything so
> it should work out ok (I avoided putting it in each bacula-director-$db
> because I don't know how to triplicate everything so the translation
> tools still work without triplicating translation work). The question is
> only asked if a bacula-director-$db package is installed.

When I was learning about how to use debconf, I was looking at putting 
the templates as bacula-director-db.templates.in and then treat them the 
same as we do with the other bacula-director-db packages, but then got 
tangled into the same question: "How do I prevent needing to triplicate 
the translation work."

My next step was trying to templatize the templates and dynamically 
creating them like with the other -db packages but then you were faster.

> In other news, I figured out why the upgrades in salsa's piuparts
> fail. Piuparts first installs e.g. bacula-director-mysql, then purges
> it. Purging does not remove the database though! The following
> installation (older version) and update (to-be-tested version) of
> bacula-director-mysql then fails of course, because the database is
> already there. Apparently the update check is only done for backports
> and experimental, which is why it works in the master branch.
> 
> https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/357

OK, that must have been annoying to track down.

> That removes the blocker on v15 from my mind. Nonetheless I'd first make
> a backport of v13 to bookworm.
I have been running a local backport for DIR, SD and FDs for my 
university since January without problems, with FDs current and older on 
all kinds of Linux versions. So we are good to go on that front.

Question: Do we want to make the text a bit more "threatening"?

---------8<---------
This update for the Bacula director comes with an upgrade of the database.
.
Upgrading the database can take many hours or even days, depending on 
the size of the database and the performance of your database server.
.
The upgrade temporarily needs around double the currently used disk 
space on the database server.
.
Please make sure there is enough disk space before continuing.
.
Running out of disk space during the upgrade might corrupt your database 
and will prevent your Bacula installation from functioning correctly.

---------8<---------

S°