package bacula-director-pgsql 7.0.5+dfsg-4ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

Thanks for filing this bug in Ubuntu.

I was able to confirm the problem on a fresh xenial container by just running:

sudo apt install bacula-director-pgsql

That pulls in the postgresql 9.5 server.

What happens is that bacula tries to reach out to postgresql on the localhost (if you accepted all bacula defaults), but postgresql is being installed in the same transaction and isn't ready yet. There isn't even a postgres user at that time. So things fail.

A couple work arounds:
a) first install postgresql-9.5, then bacula-director-pgsql
b) when bacula complains about the database, select abort, and then do "sudo apt install bacula-director-pgsql --reinstall". This time it should finish.

I believe in your case you can just run "sudo apt install --reinstall bacula-director-pgsql". I would also suggest a "sudo apt install -f" to be sure there are no remaining errors.

It worked out of the box in artful, so the fix is somewhere in between xenial and artful.

On Wed, Nov 1, 2017 at 7:26 AM, Andreas Hasenack <email address hidden> wrote:
> It worked out of the box in artful, so the fix is somewhere in between
> xenial and artful.

I would check the changes in 7.4.1~dfsg-1 or 7.4.2+dfsg-1 or 7.4.3+dfsg-1.

Also, iirc (only vaguely possibly true), bacula-director-pgsql only
depends on a postgres client, not on a postgres server. So is this
with an --install-recommends installation?

Yes, recommends are installed by default in this out-of-the box xenial container I used. And yes, postgresql (server) is a recommends only.