From: | "Lorenz, Christopher" <Christopher(dot)Lorenz(at)ZIT-BB(dot)Brandenburg(dot)de> |
---|---|
To: | 'Devrim Gündüz' <devrim(at)gunduz(dot)org>, "pgsql-pkg-yum(at)postgresql(dot)org" <pgsql-pkg-yum(at)postgresql(dot)org> |
Subject: | AW: postgis/gdal - undefined symbol: proj_crs_has_point_motion_operation |
Date: | 2024-04-30 13:16:10 |
Message-ID: | 7a701d8cf9124ea5b2f1968f734b56e9@ZIT-BB.Brandenburg.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
Hi Devrim,
Thanks a lot for the question about the proj package.
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()):
POSTGIS="3.1.11 ca03d62" [EXTENSION] PGSQL="130" GEOS="3.12.1-CAPI-1.18.1" PROJ="9.4.0" GDAL="GDAL 3.8.5, released 2024/04/02" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0" WAGYU="0.5.0 (Internal)" TOPOLO
GY RASTER
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?
Regards,
Christopher, Lorenz
-----Ursprüngliche Nachricht-----
Von: Devrim Gündüz <devrim(at)gunduz(dot)org>
Gesendet: Dienstag, 30. April 2024 11:43
An: Lorenz, Christopher <Christopher(dot)Lorenz(at)ZIT-BB(dot)Brandenburg(dot)de>; pgsql-pkg-yum(at)postgresql(dot)org
Betreff: Re: postgis/gdal - undefined symbol: proj_crs_has_point_motion_operation
Hi,
What is the output of:
rpm -qa | grep proj
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim Gündüz | 2024-05-01 09:07:27 | Re: AW: postgis/gdal - undefined symbol: proj_crs_has_point_motion_operation |
Previous Message | Devrim Gündüz | 2024-04-30 09:42:50 | Re: postgis/gdal - undefined symbol: proj_crs_has_point_motion_operation |