I am having similar problems on the RHEL8 repo. Everything is broken. Multiple geos dependencies means the postgis_raster extension is broken. If I try to use the latest postgis34 packages, then it only brings in geos312. That part works, but the problem becomes gdal36. gdal36-python-tools brings in EPEL's python3-gdal instead of PGDG gdal36-python3 from pgdg-common.
The python module "osgeo_utils" only comes with the PGDG gdal36-python3 package. That means gdal36_python-tools / gdal_calc.py is dead. I can't install gdal36-python3 on top of python3-gdal to get the osgeo_utils, because the packages conflict.
I have a big infrastructure as code project that relies on the PGDG RHEL8 repo. GDAL, postgis_raster, gdal-python-tools.... it worked earlier this month, but it's now dead in the water. Do we have a timeline here? Am I stuck retooling this to build geos, gdal, and postgis from source?
-Tim
Hi Laurenz,
That stack is completely broken, and I'm trying my best before v16 is
out.
Sorry about the inconvenience.
Regards, Devrim
On Wed, 2023-08-30 at 09:13 +0200, Laurenz Albe wrote:
> The dependencies look like this on my machine:
>
> > rpm -q --requires postgis34_16 | grep geos
> geos311 >= 3.11.2
> libgeos_c.so.1()(64bit)
>
> > rpm -q --requires postgis34_16 | grep gdal
> gdal36-libs >= 3.6.3
> libgdal.so.32()(64bit)
>
> > rpm -q --requires gdal36-libs | grep geos
> geos312
> libgeos_c.so.1()(64bit)
>
> So postgis34_16 depends on both GEOS 3.11 and GEOS 3.12.
> One dependency is direct, the other is via GDAL.
>
> Yours,
> Laurenz Albe
>
>
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR