[postgis-devel] Debian packaging and upgrade

[Paolo Cavallini]

Hi,

On 05/04/19 12:15, Christoph Berg wrote:

> I just did a jessie->stretch upgrade, and postgresql-9.4-postgis-2.1
> is indeed removed. Generally, I think we needed a few iterations to
> get everything right in the co-installability of different
> pgNN-postgisYY packages, and I'm not surprised that YY < 2.3 has bugs.
> 
> In this case, the problem is elsewhere, though. I haven't traced the
> full dependency chain down, but I think the root of the issue is that
> postgresql-9.4-postgis-2.1 transitively depends on libsigc++-2.0-0c2a
> in jessie, but in stretch, that package is being replaced by
> libsigc++-2.0-0v5, and they two are not co-installable.
> 
> Package: libsigc++-2.0-0v5
> Source: libsigc++-2.0
> Conflicts: libsigc++-2.0-0c2a
> 
> So it isn't postgis' fault that it doesn't work for jessie->stretch.
> As workaround, do a pg_dumpall before the upgrade, and manually
> restore that.

sure thing, but I think seriously breaking a cluster without warning the
user is not the way to go. Indeed leaving only the broken
postgresql-9.4-postgis-2.1 is enough to allow pg_upgradecluster.
Cheers.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/