Hi,
On Tue, 2024-04-30 at 13:16 +0000, Lorenz, Christopher wrote:
> The result was:
> $ rpm -qa | grep proj
> proj94-9.4.0-1PGDG.rhel8.x86_64
> proj82-8.2.1-3.rhel8.x86_64
> proj92-9.2.1-1PGDG.rhel8.x86_64
>
> The solution for me was to remove the old proj82 and proj92 rpms, gdal
> has used the proj92 library before.
>
> Now it works (PostGIS_full_version()):
<snip>
Great!
> The automatic update on my server doesn't removes the old proj92
> package. Is it possible and practical to define conflicts with
> different proj versions in specs to avoid problems like these?
I am not sure this is 100% safe. What happens when there is a PostGIS
version that cannot be compiled against newer Proj and someone wants to
install multiple PostGIS versions?
I'm not saying that the current situation is ok, just saying that I'm
not satisfies with the solutions that I thought so far.
Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR