Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwocB-00044v-Dr for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 21 Feb 2019 13:42:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gwoc9-0001AQ-Fd for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 21 Feb 2019 13:42:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwoc9-0001AJ-6X for pgsql-pkg-yum@lists.postgresql.org; Thu, 21 Feb 2019 13:42:13 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwoc6-0007p9-BN for pgsql-pkg-yum@postgresql.org; Thu, 21 Feb 2019 13:42:12 +0000 Received: by mail-wr1-x441.google.com with SMTP id w17so30207184wrn.12 for ; Thu, 21 Feb 2019 05:42:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crunchydata-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vasQ2vClpNKskVNQO4Q/P+lYb3k9Emxi34clTt7TP3M=; b=J/kGevoHEE68OXd5W2OR3lEAF/V2PzZ+78hEXm+5aGE6QfW56XtiUcdiKe5VYmL7qn mdxi3fBpzk2gOmC7GS5kIo7ZoFcja7ezRQUwL/KSKT/vJeDDAZivwCpMjc5TVuYVLjoK Ss6z+obcILNFsxAxLBnL9qSwT9hGbfbREM9osYx2uWVafH9+mRo/Kv43iuPvoZyVhgjq wvK+jqgF8+pnm+az3y8wjMKupwVJ/B7cNKseIGnI6t+OU8BTnlskUrZXYYRs/b2sbiW1 Js/SRGh02ZyR5n/r/jDNDG7T/sJNKZUcGk1mBU1ojO3MIXMDSMKiycXxSe5+Xi640foz ywEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=vasQ2vClpNKskVNQO4Q/P+lYb3k9Emxi34clTt7TP3M=; b=t6yVf2+LLYuZq0ljolsro4N+ZydfT9MHjrJ6KZUpOSrhSCzl96LXbcxQ8y34vTH4lW fXhUx10Voefn0GSnnzgr4qBr1Mo8lHG2uzU8I+1Xgl/BTu9nnkZDkPp3JgeBGIvXZ+kv P4PWomzO2Dd0CZmatR6Zpl8JVKAATUQfspBmJ58kZrusSBXhk5oMjJAnveI2Izusx7Lf pQ1J6+Fecw9Gl4m2+xwyTIhI71ATPd0GIrfK7rs9wLWG/syVdIyBNJ1ulbIumzZiKgKk PWmy3W4QeNDc33twNfJveSMXBn224KjI2Qr9oyUNSZJZg+371FbsrFM5s9iL6d/ESA42 YPBw== X-Gm-Message-State: AHQUAuYKI6tnRnjZIoR1MfGYz1zJJV4F3m6pU3ATbdNHof0fVSQhMK4Z QxSA5GZNhaebvJgIF6xwUtg25JfqmWMrmronZq50 X-Google-Smtp-Source: AHgI3IZifzHaE4t2fj0Y/ZS2KusGc07dObWoplf4879SwrYuS4Lr3UEgsM+DA437YKc0c7xQOu620aI8apHJN8enBy4= X-Received: by 2002:a5d:4a8a:: with SMTP id o10mr28670085wrq.189.1550756528808; Thu, 21 Feb 2019 05:42:08 -0800 (PST) MIME-Version: 1.0 References: <20181210150643.GF4848@telsasoft.com> <20181219202107.GA5406@telsasoft.com> <20190107215410.GA22493@telsasoft.com> <20190221132606.GC5238@msg.df7cb.de> In-Reply-To: <20190221132606.GC5238@msg.df7cb.de> From: John Harvey Date: Thu, 21 Feb 2019 08:41:32 -0500 Message-ID: Subject: Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7 postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so: undefined symbol: geod_polygon_init To: Christoph Berg , Justin Pryzby , pgsql-pkg-yum Content-Type: multipart/alternative; boundary="00000000000008835c058267a47a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000008835c058267a47a Content-Type: text/plain; charset="UTF-8" Hi Christoph (and others), 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. Regards, -John ----------------------- John Harvey (843) 628-5421 Crunchy Data Enterprise PostgreSQL www.crunchydata.com On Thu, Feb 21, 2019 at 8:26 AM Christoph Berg 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 > > Why does postgis-2.4.so even "see" the geos37 package? > > > [pryzbyj@template0 ~]$ ldd /usr/pgsql-11/lib/postgis-2.4.so > > libgeos_c.so.1 => /usr/geos36/lib64/libgeos_c.so.1 > (0x00007f3e50e6e000) > > libgeos-3.6.2.so => /usr/geos36/lib64/libgeos-3.6.2.so > (0x00007f3e4f12e000) > > > > Fixed with: rpm -e geos36-3.6.2-3.1.rhel7.x86_64 > > Should declare the RPM equivalent of debian's "Breaks" ?? > > Christoph > > --00000000000008835c058267a47a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Christoph (and others),

=
I believe the issue that remains could be pretty easily fixed when Dev= rim releases geos 3.7.0-2.=C2=A0 That patch version contains an Obsoletes s= o that geos37 will obsolete geos36, which I think would solve the functiona= lity problem.=C2=A0 I did some testing locally with that change, and it see= med to work.=C2=A0 Since geos37 only adds functionality on top of geos36 an= d 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.

Regards,
=C2=A0 -John

<= div>
-----------------------
John Harvey
(84= 3) 628-5421
Crunchy Data
Enterprise PostgreSQL=C2=A0


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.=C2=A0 See earlier= communiction,
> copied below.
>
> Just reinstalling postgis on a centos7 test server which previously ra= n
> 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=3D# \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:=C2= =A0 could not load library "/usr/pgsql-11/lib/postgis-2.4.so": /u= sr/pgsql-11/lib/postgis-2.4.so: undefined symbol: GEOSFrechetDistanceDensif= y

This has just popped up again on IRC, with postgis24_96-2.4.6-3.rhel7.x86_6= 4

Why does postgis-2.4.so even "see" the geos37 package?

> [pryzbyj@template0 ~]$ ldd /usr/pgsql-11/lib/postgis-2.4.so
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0libgeos_c.so.1 =3D> /usr/geos36/li= b64/libgeos_c.so.1 (0x00007f3e50e6e000)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0libgeos-3.6.2.so =3D> /usr/geos3= 6/lib64/libgeos-3.6.2.so (0x00007f3e4f12e000)
>
> Fixed with: rpm -e geos36-3.6.2-3.1.rhel7.x86_64
> Should declare the RPM equivalent of debian's "Breaks" ?= ?

Christoph

--00000000000008835c058267a47a--