[Debian-astro-maintainers] Bug#984555: gavodachs2-server: fails to install/upgrade.
Markus Demleitner
msdemlei at ari.uni-heidelberg.de
Wed Mar 17 10:09:15 GMT 2021
On Tue, Mar 16, 2021 at 10:49:24AM +0100, Markus Demleitner wrote:
> What is already making me nervous at a second glance: There's
> postgresql-11-pgsphere, but on bullseye postgres will be postgres 13.
> I'd hence suspect that the postgres DaCHS is talking to is not the
> one that has pgsphere.
Meanwhile, I'm pretty sure this is what happened here: You already had
a postgres 11 on your boxes, but at some point a postgres 13 was put
on the box as well, while postgres 11 lingered around.
Now, when installing DaCHS, the system satisified the pgsphere
dependency with postgres-11-pgsphere. This, however, means that
there is no pgsphere on the operational pgsphere, which is what kills
DaCHS (and, really, there is very little point running DaCHS without
these extensions, which is why it doesn't even try to limp on).
Summing up: If you un-install postgres 11, things should start to
work.
Is there a good way to prevent this confusing situation? I don't
know, but I'll ask around.
-- Markus
More information about the Debian-astro-maintainers
mailing list