On Thu, 2024-03-28 at 09:35 +0000, Devrim Gündüz wrote:
> > Thanks for fixing!
>
> I did not fix anything :-( No idea what happened, as I also tried with a
> fresh vm yesterday and it worked as well...
Mysterious, but no problem.
However, I found a more serious problem:
The PostGIS dependencies for the latest package seem to be messed up.
Let's check what PROJ and GDAL versions are required by PostGIS:
> rpm -q --requires postgis34_16 | grep -e '\(proj\|gdal\)'
gdal38-libs >= 3.8.4
libgdal.so.34()(64bit)
libproj.so.25()(64bit)
proj93 >= 9.3.1
Ok, cool. Now let's look at the requirements for gdal38-libs:
> rpm -q --requires gdal38-libs | grep '\(libspatialite\|devel\)'
libgeotiff17-devel
libspatialite.so.8()(64bit)
libspatialite50-devel
There is a strange thing: it requires development packages. Huh?
But let's follow the other dependency:
> rpm -q --whatprovides 'libspatialite.so.8()(64bit)'
libspatialite50-5.1.0-2PGDG.f39.x86_64
That's not particularly surprising. But that package requires PROJ too:
> rpm -q --requires libspatialite50 | grep proj
libproj.so.25()(64bit)
proj92 >= 9.2.1
So PostGIS ends up requiring both proj92 and proj93.
Since both packages seem to provide the same major library version,
I guess that libspatialite50 should be changed to require proj93.
Yours,
Laurenz Albe
