BUG #14991: postgis-2.4.so: undefined symbol: GEOSMinimumClearance
The following bug has been logged on the website:
Bug reference: 14991
Logged by: Xavier Corredor Llano
Email address: xavier.corredor.llano@gmail.com
PostgreSQL version: 10.1
Operating system: Centos 7
Description:
Hi everyone,
I'm using the official repository for Postgres 10.1 in Centos 7, I have a
web page with postgresql 10.1 + postgis 2.4 + psycopg2 + django + python
3.6. The DB, connexion and all work fine a week ago, two days ago I made
update the system (some packages were updated like geos36, proj49,
postgis..) and the connexion have broken with problems with postgis:
psycopg2.InternalError: the library could not be loaded
«/usr/pgsql-10/lib/postgis-2.4.so»: /usr/pgsql-10/lib/postgis-2.4.so:
undefined symbol: GEOSMinimumClearance
the complete log: https://pastebin.com/WupetTZ7
Thanks,
Xavier
Hi,
On Thu, 2017-12-21 at 21:26 +0000, PG Bug reporting form wrote:
Bug reference: 14991
Logged by: Xavier Corredor Llano
Email address: xavier.corredor.llano@gmail.com
PostgreSQL version: 10.1
Operating system: Centos 7
Description:Hi everyone,
I'm using the official repository for Postgres 10.1 in Centos 7, I have a
web page with postgresql 10.1 + postgis 2.4 + psycopg2 + django + python
3.6. The DB, connexion and all work fine a week ago, two days ago I made
update the system (some packages were updated like geos36, proj49,
postgis..) and the connexion have broken with problems with postgis:psycopg2.InternalError: the library could not be loaded
«/usr/pgsql-10/lib/postgis-2.4.so»: /usr/pgsql-10/lib/postgis-2.4.so:
undefined symbol: GEOSMinimumClearance
Thanks for the report. Please update to PostGIS 2.4.2-5, and GeOS 3.6.2-3.1,
which fixes this issue.
Apologies for the delay and inconvenience. It took some time to stabilize
things.
Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR