Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eHXR4-00040F-Jk for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 22 Nov 2017 15:59:38 +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 1eHXR3-0007OM-E5 for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 22 Nov 2017 15:59:37 +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 1eHXR3-0007OC-6X for pgsql-pkg-yum@lists.postgresql.org; Wed, 22 Nov 2017 15:59:37 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eHXQw-0001nc-7j for pgsql-pkg-yum@postgresql.org; Wed, 22 Nov 2017 15:59:36 +0000 Received: from asus-laptop04 (unknown [78.183.66.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 0CC643FCA8 for ; Wed, 22 Nov 2017 15:59:26 +0000 (UTC) Message-ID: <1511366364.3655.8.camel@gunduz.org> Subject: Heads up: Potential PostGIS breakage is coming From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: pgsql-pkg-yum Date: Wed, 22 Nov 2017 18:59:24 +0300 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-0R/zxJoBjQeU99NILLTh" X-Mailer: Evolution 3.26.2 (3.26.2-1.fc27) Mime-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --=-0R/zxJoBjQeU99NILLTh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. Thanks! Regards, =20 --=20 Devrim G=C3=BCnd=C3=BCz EnterpriseDB: https://www.enterprisedb.com PostgreSQL Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-0R/zxJoBjQeU99NILLTh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEH8GKHNUOKtDEiyD22MM9/pLPbrUFAloVntwACgkQ2MM9/pLP brUKsg//YqS8EvOUWD6DJgiryRWwfgjywyZTp2WWm3agvQHwTbBJg6BAKmB9EW/i AUYW6zHMZSOSdwGpxPZcRqWp7VURfpraBdwjQKe6YfH4DbpPb6fWxHUoqBqOLWD7 dRpjmEFewgWtDXIo/NW1CpcUfV0QDMtkorLanug7d+lmkDIFjUIFqU9bPzQUKDwr PVEyT/VDMYqVXyx5yLIEXxI2QRxnz/cv5qvL1nqc8qklQak1lNSjLQxaRKIz6ZKW PPVB6eS23hk+tYgQUYphiPx4dCMcByF76okACWuuNeC1zP+k8M2MSJTThht2Txaw t2QLgRrM+hFTCWOKuk1rj9QulqbZJuiNdAMYmhjg4hTseFVxeJbuYAtLtF0hAmyJ bLLBJ0FClCkt+zemElpuJk1wJ0aSQI3lv1+aPzaNkJnWjtMdQDvk8XuC3P9DuuQi ftM+WKumMysrO7OcgRYFS7Ah5ch1DDjHnYdzVTlnyrU8H0Tx1+JkZou47SSIhRJm fBxCKSRzvKC6sZxesFt7k/rzAhuiYm1I4RMoGz/9DB+ewoJjnmxmUtZOt0oUky0v moA0hW34h4NkCA0oKj4qFzTx0EpS4b36LjJ4loYo787hBoQcLA/tbcGjauhm4Cc0 mzML9S1wSLh4Roe4MX76L+TZMerhtymuxSASbKJTu0cSvfVld8o= =uQdP -----END PGP SIGNATURE----- --=-0R/zxJoBjQeU99NILLTh--