From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
Cc: | pgsql-pkg-yum(at)postgresql(dot)org |
Subject: | Re: postgis for beta releases |
Date: | 2020-07-21 18:16:39 |
Message-ID: | 20200721181639.GK5748@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote:
>
> Hi,
>
> On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote:
> > Would you consider building packages during beta ?
>
> You mean PostGIS 3.1? I thought I pushed it already :(
>
> Built packages now. They will sync soon to v13 testing repos. Would
> you like me to build against v12 as well?
Thanks - I see that postgis31 is available for postgres13.
As I mentioned, I think postgis30 should *also* be built for v13, and postgis31
should *maybe* be built for v12:
On Sat, Jul 11, 2020 at 11:46:20AM -0500, Justin Pryzby wrote:
> I think the postgis that exists for the stable release(12) should also be built
> for the beta release(13). That allows test upgrades by 1) installing same
> postgis for new postgres; and 2) pg_upgrade.
>
> Whether to build a new version of postgis is a separate question, but if you
> do, I'd suggest to build for both versions of postgres when possible. That
> allows choice of which to upgrade first.
>
> During beta period in previous years, postgis has been the one important thing
> missing. That requires us to drop our postgis columns for beta testing. Last
> year for the first time, I instead built postgis locally on a couple servers.
>
> I think most packages aren't built for beta, which is no problem (although I
> think they sometimes needed to be added after the fact). These are on our
> list: pg_repack, fincore, libpqxx-devel.
From | Date | Subject | |
---|---|---|---|
Next Message | ANASTACIO Tiago | 2020-07-23 14:45:09 | pgbackrest dependency missing |
Previous Message | Justin Pryzby | 2020-07-21 18:10:12 | v13 debug pacakges |