I believe the issue that remains could be pretty easily fixed when Devrim releases geos 3.7.0-2. That patch version contains an Obsoletes so that geos37 will obsolete geos36, which I think would solve the functionality problem. I did some testing locally with that change, and it seemed to work. Since geos37 only adds functionality on top of geos36 and has no breaking changes, it should be an okay solution to solve the "having 2 geos's on at the same time is a problem" issue.
On Thu, Feb 21, 2019 at 8:26 AM Christoph Berg <myon@debian.org> wrote:
Re: Justin Pryzby 2019-01-07 <20190107215410.GA22493@telsasoft.com> > This appears to be more or less same as issue #3710. See earlier communiction, > copied below. > > Just reinstalling postgis on a centos7 test server which previously ran > postgres 11 beta. > > Installing : geos37-3.7.0-1.rhel7.1.x86_64 > Installing : postgis24_11-2.4.6-3.rhel7.x86_64 > Installing : postgis24_11-client-2.4.6-3.rhel7.x86_64 > > sentinel=# \i /usr/pgsql-11/share/contrib/postgis-2.4/postgis.sql > BEGIN > SET > DO > CREATE FUNCTION > psql:/usr/pgsql-11/share/contrib/postgis-2.4/postgis.sql:95: ERROR: could not load library "/usr/pgsql-11/lib/postgis-2.4.so": /usr/pgsql-11/lib/postgis-2.4.so: undefined symbol: GEOSFrechetDistanceDensify
This has just popped up again on IRC, with postgis24_96-2.4.6-3.rhel7.x86_64