[pkg-bacula-devel] Bug#923444: bacula: autopkgtest regressed in buster

Sven Hartge sven at svenhartge.de
Sun Mar 3 15:18:26 GMT 2019

On 03.03.19 14:32, Paul Gevers wrote:

> I rather propose that we accept the current regression of the bacula
> autopkgtest and we fix the situation properly (in autopkgtest and/or
> dbconfig-common) after the buster release.

The right package to fix this is dbconfig, IMHO, because the situation
here can also happen when a user installs the packages manually. If the
database engine is configured after bacula-director-DBNAME, the problem
may happen.

I have not yet tested, whether apt/dpkg alter the order installation in
those two cases:

apt install bacula postgresql
apt install bacula

Both should select postgresql, the last one via Recommends:, the first
one via directly installing it.

> Can you live with that?

It is not my place to say, Carsten must decide this, but the question
also is: can the debian-ci people live with that?


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

More information about the pkg-bacula-devel mailing list