[pkg-bacula-devel] Piuparts / Upgrade confirmation [was Re: Change systemd unitdir to /usr/lib/systemd. (Closes: #1065313)]

[Carsten Leonhardt]

Sven Hartge <sven at svenhartge.de> writes:

>> Possibly unattended upgrades will fail because I default to "abort the
>> upgrade". Like in piuparts.
>
> Can we detect a non-interactive upgrade and not ask the question?

Maybe. But we'd also skip the question on all other non-interactive
upgrades. I'd prefer not to do that.

>> I've put the confirmation in the common bacula-director package for now,
>> probably it's a bad idea because the database specific packages can be
>> installed without having the director installed (whatever sense that
>> makes).
>>
>> Maybe the database specific director packages should also have a
>> "Depends: bacula-director" anyway?

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.


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

That removes the blocker on v15 from my mind. Nonetheless I'd first make
a backport of v13 to bookworm.

 - Carsten