| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | pgsql-pkg-yum(at)lists(dot)postgresql(dot)org,Daniel Farina <daniel(at)citusdata(dot)com> |
| Subject: | Re: Heads up: Potential PostGIS breakage is coming |
| Date: | 2017-11-27 22:08:14 |
| Message-ID: | 48482592-9247-4850-B575-B4BAB84C4F44@gunduz.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
Hi Daniel,
Thank you for the feedback!
Can you please update the packages? I pushed a fix for this last week.
Regards, Devrim
On 27 November 2017 22:04:58 GMT+00:00, Daniel Farina <daniel(at)citusdata(dot)com> wrote:
>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.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2017-11-27 22:11:36 | Re: Heads up: Potential PostGIS breakage is coming |
| Previous Message | Daniel Farina | 2017-11-27 22:04:58 | Re: Heads up: Potential PostGIS breakage is coming |