Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZIIG-0008Vj-Jw for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 10 Jan 2018 15:27:56 +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 1eZIIF-0000yX-PH for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 10 Jan 2018 15:27:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eZIIF-0000yM-Kf for pgsql-pkg-debian@lists.postgresql.org; Wed, 10 Jan 2018 15:27:55 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eZIIC-00034O-I4 for pgsql-pkg-debian@postgresql.org; Wed, 10 Jan 2018 15:27:54 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 3zGtDl2jqpz3F41; Wed, 10 Jan 2018 16:27:51 +0100 (CET) Date: Wed, 10 Jan 2018 16:27:51 +0100 From: Christoph Berg To: Keiko Oda Cc: pgsql-pkg-debian@postgresql.org Subject: Re: postgis 2.3.5 releases Message-ID: <20180110152750.GD532@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Keiko Oda , pgsql-pkg-debian@postgresql.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Re: Keiko Oda 2018-01-10 > Hello, > > I'd like to have Postgis 2.3.5 (or 2.3.4) package with Postgres 10 or > earlier, but seems like the available package is only 2.3.3 for now. 2.3.3 > doesn't support Postgres 10, therefore, there is no combination of Postgres > 10 + 2.3.x. > Seems like Postgis 2.4.2 was shipped before (which was released at the same > timing as 2.3.5), but 2.3.5 wasn't included with this update. > > https://www.postgresql.org/message-id/E1eKUi8-0005gA-N9%40atalia.postgresql.org > > Is there some open issue that makes it hard to ship 2.3.5 right now? We are not supporting several postgis major releases in parallel, just the latest one. The packaging would be considerably more complex, which we didn't want to go through. Old packages for 2.3.2 are available via http://atalia.postgresql.org/morgue/p/postgis/ Christoph