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

[Paul Gevers]

Hi,

On 28-02-2019 13:17, Sven Hartge wrote:
> After this, everything else falls apart, because neither does the bacula
> user nor the database exist.
>
> Why can't bacula-director-pgsql depent on postgressl-server? Because we
> support a remote database.

As the maintainer of dbconfig-common, I recognize this fully.

> Looking at the older autopkgtest logs, one can see that up 2019-02-23
> 01:38:30 UTC the package "postgresql-11" was installed and configured
> before bacula-director-pgsql.
> 
> Then, on 2019-02-25 02:18:41 UTC something changed outside of the bacula
> packages and the order in which those two packages get configured
> reversed, causing the problems.

Ack. So for whatever reason the order used to work, but now it doesn't
anymore. There is no mechanism to force the order. So, how to fix this
in the autopkgtest? Could you check if the database exists and if not,
trigger reconfig of bacula at the start of your test? Would that solve
the issue? Another (but extremely ugly) way could be to not have bacula
installed as a test dependency and install it yourself at the beginning.
Please try to avoid that last idea.

Paul