Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lUYXJ-0004nE-Lm for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 08 Apr 2021 17:33:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lUYXF-0001OE-Pm for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 08 Apr 2021 17:33:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lUYXF-0001O7-Gn for pgsql-pkg-debian@lists.postgresql.org; Thu, 08 Apr 2021 17:33:41 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lUYXC-0007lj-LZ for pgsql-pkg-debian@lists.postgresql.org; Thu, 08 Apr 2021 17:33:41 +0000 Received: by mail-ej1-x634.google.com with SMTP id n2so4407922ejy.7 for ; Thu, 08 Apr 2021 10:33:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8bH2kIxq3VgrJufjvurKtRzZve1Counv7wJuRZZgBS4=; b=gB5BxpoGcfwmzkwPyCk0R0E4UzNn5JwHFWmXz/rlpcLr3QKNaatCiZBAO17DhmhIIf otOlcdcMIdn73AdA7Qyo+/z7gfSTK659qSCbmpsdOOoKZV7nEQHjPu0k7zcONHM2RpjQ rGZRF5rBcFbUiWZozTIlqCRWOpUHY93PlEdxlkkpkuK4QfxhfwFZsbaC5N8YINekvoo4 rnbK3xnAodB1OaLR/pOkuIbjLvULt+PkPu1j+9v2FHmoOOQIKE6UvwICf3wmB2pg9TFv fM2coilxrlpKiAGnHf2f0rJsQGThZNSow4Kx4Dm+/eJ05h2xVTJKDMOZcmSRFzEy0Oyq mY2g== 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=8bH2kIxq3VgrJufjvurKtRzZve1Counv7wJuRZZgBS4=; b=tlme13R4nBKxeCQYzGybo0C3E68aVG1+m7muDIhTvZ0/2sLpDBrGYuf8LMOvrgbh1P f7a60Uw5enbkDaxLKiEJlXolw81jDaGutRwLx/hGzmzx2DKnmDho0ZLXnMkwtzNzr5Es jHge/zmYLvgqTRRenxNC41TaNGm1iioAsqrXpi6UllT2Tmi4rubFULPJ3k47B5CYR3G9 AuIipe6SG79RArPpwN5hAkoV1fzsLocvN/ngwWfa42zHeVyWurpV32T5JXq+D1COhxHs L3qVhNN+3VVCPNzX4cFnn7QCuEA458VHG3D9GJnThX3lTyC+y3PAflAjNPivFSdb0n6w 4UCQ== X-Gm-Message-State: AOAM532wA9r5Hw/CC42JTz2Glbeu/4AZU1DD5rcXIFl1eVUIF9QXHqY/ dXhag9VfAjUcFyQDh0b927yYOM+212eorSNKqYI= X-Google-Smtp-Source: ABdhPJz21RIl5F7c0Oe5CayL/ObV6/lEYUMx+hY10L2rqLq2raK8dwD3W3JzBScFeFMeOBqjFyrGhoCEw8RFY4iY4LE= X-Received: by 2002:a17:906:f9c3:: with SMTP id lj3mr1058695ejb.134.1617903217794; Thu, 08 Apr 2021 10:33:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Imre Samu Date: Thu, 8 Apr 2021 19:33:26 +0200 Message-ID: Subject: Re: Plans for GEOS 3.9 packaging? To: Andreas Neumann Cc: pgsql-pkg-debian@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000093e26f05bf797291" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000093e26f05bf797291 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > We have plans to update our DB in November or December 2021 > and it would be great if GEOS 3.9.x would be available in the PGDG-Repo then? my proposal : * "debian:bullseye" (debian11) * - now this is in "Hard Freeze" ; expected this calendar year. [1] in my version: root@869f5a20e970:/# apt list --installed | grep -E 'geos|postgis|proj|gdal= ' gdal-data/now 3.2.1+dfsg-1 all [installed,local] *libgdal28/now 3.2.1*+dfsg-1+b1 amd64 [installed,local] *libgeos-3.9.0*/now 3.9.0-1 amd64 [installed,local] libgeos-c1v5/now 3.9.0-1 amd64 [installed,local] *libproj19/now 7.2.1-1* amd64 [installed,local] *postgresql-13-postgis-3-scripts/now 3.1.1+dfsg-1.pgdg110+1 all [installed,local]* postgresql-13-postgis-3/now 3.1.1+dfsg-1.pgdg110+1 amd64 [installed,local] proj-data/now 7.2.1-1 all [installed,local] [1] https://www.phoronix.com/scan.php?page=3Dnews_item&px=3DDebian-11.0-Hard-Fr= eeze I am a contributor in https://github.com/postgis/docker-postgis ; and now I am testing the bullseye version. ( postgis3.1+Geos3.9) :) The other alternative: the "postgis/postgis:13-master" image ( https://github.com/postgis/docker-postgis/tree/master/13-master ) Imre Andreas Neumann ezt =C3=ADrta (id=C5=91pont: 2021. =C3= =A1pr. 8., Cs, 18:15): > Hi, > > I was wondering if you have plans to package GEOS 3.9.x together with > Postgis 3.1 during the year 2021? > > In my day job I would need to use some new Postgis 3.1 functions that are > only available if Postgis was compiled against GEOS 3.9.x, such as > https://postgis.net/docs/ST_MaximumInscribedCircle.html - and we would > also like to use the new gridSize parameters for limited accuracy in the > Overlay functions. Those are also only available if Postgis was compiled > against GEOS 3.9 > > Our sysadmins only want to install official Debian and PGDG-Repo packages= . > We have plans to update our DB in November or December 2021 and it would = be > great if GEOS 3.9.x would be available in the PGDG-Repo then? > > Thank you for your reply, > Andreas > > -- > Andreas Neumann > QGIS.ORG board member (treasurer) > --00000000000093e26f05bf797291 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>=C2=A0 We have plans to update our DB in November= or December 2021=C2=A0
> and it would be great if GEOS 3.9.x = would be available in the PGDG-Repo then?

my propo= sal :=C2=A0 "debian:bullseye" (debian11)=C2=A0=C2=A0
=
-=C2=A0 now this is in "Hard Freeze" ; expected this calenda= r year. [1]

in my version:
root@869f5a20e970:/# apt list --installed | grep= -E 'geos|postgis|proj|gdal'

gdal-data/now 3.2.1+dfsg-= 1 all [installed,local]
libgdal28/now 3.2.1+dfsg-1+b1 amd64 [inst= alled,local]
libgeos-3.9.0/now 3.9.0-1 amd64 [installed,local]libgeos-c1v5/now 3.9.0-1 amd64 [installed,local]
libproj19/now 7.2.1= -1 amd64 [installed,local]
postgresql-13-postgis-3-scripts/now 3.= 1.1+dfsg-1.pgdg110+1 all [installed,local]
postgresql-13-postgis-3/n= ow 3.1.1+dfsg-1.pgdg110+1 amd64 [installed,local]
proj-data/now 7.2.1-1 = all [installed,local]


I am a contributor in=C2=A0https://github.com/postgis/d= ocker-postgis ;=C2=A0=C2=A0
=C2=A0 =C2=A0and now I am testing= the bullseye version.=C2=A0 ( postgis3.1+Geos3.9)=C2=A0 =C2=A0:)=C2=A0
=
The other alternative:=C2=A0 =C2=A0the "postgis/postgis:13-= master" image=C2=A0 (=C2=A0 https://github.com/postgis/docker-postgis= /tree/master/13-master )

Imre
=


Andreas Neumann <and= reas@qgis.org> ezt =C3=ADrta (id=C5=91pont: 2021. =C3=A1pr. 8., Cs, = 18:15):
Hi,

I was wondering if you have plans to package GEOS 3.9.x together with Pos= tgis 3.1 during the year 2021?

In my day job I wou= ld need to use some new Postgis 3.1 functions that are only available if Po= stgis was compiled against GEOS 3.9.x, such as https://postgis.n= et/docs/ST_MaximumInscribedCircle.html - and we would also like to use = the new gridSize parameters for limited accuracy in the Overlay functions. = Those are also only available if Postgis was compiled against GEOS 3.9
<= /div>

Our sysadmins only want to install official Debian= and PGDG-Repo packages. We have plans to update our DB in November or Dece= mber 2021 and it would be great if GEOS 3.9.x would be available in the PGD= G-Repo then?

Thank you for your reply,
Andreas

--
A= ndreas Neumann
QGIS.= ORG board member (treasurer)
--00000000000093e26f05bf797291--