Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJRWb-0008EK-LZ for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 27 Nov 2017 22:05:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJRWb-0000l6-7h for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 27 Nov 2017 22:05:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eJRWa-0000ka-Vu for pgsql-pkg-yum@lists.postgresql.org; Mon, 27 Nov 2017 22:05:13 +0000 Received: from mail-yw0-x231.google.com ([2607:f8b0:4002:c05::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eJRWY-00023t-Ku for pgsql-pkg-yum@postgresql.org; Mon, 27 Nov 2017 22:05:11 +0000 Received: by mail-yw0-x231.google.com with SMTP id g193so2239926ywe.3 for ; Mon, 27 Nov 2017 14:05:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citusdata.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=24eKuL1B1wH4G1xDeFjE+1s/4qbKP4OGFiMURCKIzUo=; b=MAWCoatPjMkrF6hEKVWS//L5I639qAdHtm0+05hoxMQjhz4JIJtGqAHEfAkyJ03Wzs xwdzFDZSlRBCTGOUB9jxUJJaS3fWNc7Q1CeLyYaPx5ssOAEu6hHBmWedte3h1qOtqDEU qZUWKHJtdSIJY+z5bO/czUFiOmEqlX0Mnx3bc= 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:cc; bh=24eKuL1B1wH4G1xDeFjE+1s/4qbKP4OGFiMURCKIzUo=; b=W4ZGs+bq2ZzXzY11QsVM/PoCb6gWYJW+09Y+c4afOb0Y4DEONMLwGcCj0ii//sIn0l GHy+gnFbADZr1vkcfvFp13E5fLl8nxxKCYDb3l5flALPnhZefgM/AotvxvBqVVfni9vD SMF03IjIGNFdCv9mPouqnA+hsbDmSPnrgBSgnkfm/H3DpF93JdjOEmSCeHgz3ALtpy4F eRHneTj8NIb2vE4HmXxlGhvILHUHfDo+ze5TCTRwlTpXSCNagB4o8Hg5AshoGTRtYHu5 UQsEVDLRhr0nRnGg7RkRYdY+85qOgKxeGKoFtzdfjHtWvtboViWn/QfsEqRbE5/da82o Y0Vw== X-Gm-Message-State: AJaThX5XcwrsoHLyNeP2DwrDkGD7lCVwLhG64XsADX4LLv3XhOvZL0F9 JO7DmV/aPk3rKaRVJ/QI3BE6TMM5Mh2YasBA/1W4YA== X-Google-Smtp-Source: AGs4zMZSDlO+AjC2y7zPZHjiGxSbb8Jt1/fg95Pxi83lZkii/mQRSsA+tz118qUWPFEKDStOWp65ypt0ehnzIVSD5Ro= X-Received: by 10.13.242.196 with SMTP id b187mr607138ywf.16.1511820309424; Mon, 27 Nov 2017 14:05:09 -0800 (PST) MIME-Version: 1.0 References: <1511366364.3655.8.camel@gunduz.org> In-Reply-To: <1511366364.3655.8.camel@gunduz.org> From: Daniel Farina Date: Mon, 27 Nov 2017 22:04:58 +0000 Message-ID: Subject: Re: Heads up: Potential PostGIS breakage is coming To: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= Cc: pgsql-pkg-yum Content-Type: multipart/alternative; boundary="94eb2c034010820b89055efe1845" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --94eb2c034010820b89055efe1845 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 22, 2017 at 7:59 AM Devrim G=C3=BCnd=C3=BCz = wrote: > > Hi, > > I am about to push PostGIS 2.4.2-2 packages to 10-testing repos. Unlike t= he > 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, b= ut > 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. --94eb2c034010820b89055efe1845 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, No= v 22, 2017 at 7:59 AM Devrim G=C3=BCnd=C3=BCz <devrim@gunduz.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 geos3= 6
(GeOS 3.6) packages, which installs to non-standard directories (/usr/proj4= 9
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 introdu= ce
GeOS 3.7 support to our repo, when it is released.

I read some reports about proj 4.8 reporting incorrect results, that trigge= red
this package process.

So, I will be happy if someone can test by enabling PG 10 testing repositor= y,
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 rel= ation to geos36, requires some ldconfig files.

--94eb2c034010820b89055efe1845--