| From: | Daniel Farina <daniel(at)citusdata(dot)com> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | pgsql-pkg-yum <pgsql-pkg-yum(at)postgresql(dot)org> |
| Subject: | Re: Heads up: Potential PostGIS breakage is coming |
| Date: | 2017-11-27 22:04:58 |
| Message-ID: | CAOPfGFjPbndFVVNJM82LD1bZiDgBr5JZHe451+0kMkG5NucBXQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
On Wed, Nov 22, 2017 at 7:59 AM Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
>
> Hi,
>
> I am about to push PostGIS 2.4.2-2 packages to 10-testing repos. Unlike the
> other packages, the new packages will depend on proj49 (Proj 4.9) and
> geos36
> (GeOS 3.6) packages, which installs to non-standard directories
> (/usr/proj49
> and /usr/geos36, respectively), so won't conflict with the OS packages, but
> will use recent versions of Proj and GeOS. With this change, we can
> introduce
> GeOS 3.7 support to our repo, when it is released.
>
> I read some reports about proj 4.8 reporting incorrect results, that
> triggered
> this package process.
>
> So, I will be happy if someone can test by enabling PG 10 testing
> repository,
> and see if things are broken or not.
>
>
I think postgis is not dynamically linking properly to proj. It finds the
path fine when compiling, though. Perhaps it, like libproj49 itself in
relation to geos36, requires some ldconfig files.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2017-11-27 22:08:14 | Re: Heads up: Potential PostGIS breakage is coming |
| Previous Message | Nicolas Thauvin | 2017-11-27 16:22:58 | pgloader depends on psycopg |