On Tue, 18 May 2021 20:36:23 +0200 Dennis Filder <d.fil...@web.de> wrote:
One more observation: Bullseye's gdal-data 3.2.1+dfsg-1 defines a Breaks: libgdal20 (< 2.5.0~), but the libgdal20 in Buster is 2.4.0, and postgresql-11-postgis-2.5 depends on that. libgdal28 depends on gdal-data (>=3.2.1+dfsg-1). To me it looks like there's no way to keep postgresql-11-postgis-2.5 around if anything that depends on libgdal28 (postgis, libopencv-imgcodecs4.5, ...) gets installed.
What would be needed to reintroduce postgresql-11-postgis-2.5 (i.e. src:postgis-2.5) (built against bullseye libraries) into bullseye? Probably libraries and -dev packages from postgresql-11, too. Here I assume that src:postgis-2.5 could be built against gdal 3.2.x and that can be used to perform the upgrade to postgis 3.x - is that true?
Andreas
