public inbox for [email protected]
help / color / mirror / Atom feedFrom: Justin Pryzby <[email protected]>
To: Devrim Gündüz <[email protected]>
Cc: Paul Ramsey <[email protected]>
Cc: Christoph Berg <[email protected]>
Cc: [email protected]
Subject: Re: postgis for beta releases
Date: Thu, 18 Aug 2022 08:38:37 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<YKa6VDK/[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Wed, Jul 13, 2022 at 03:09:02PM +0100, Devrim Gündüz wrote:
> Hi Justin,
>
> On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote:
> > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote:
> > > I'm not sure if it's too early to ask, but would you consider
> > > building postgis
> > > for pg15b1 ?
> >
> > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote:
> > > Also, it looks like there's no entry in the yum repo file for
> > > pgdg15-updates-testing-debuginfo.
> >
> > Checking back about these parts.
>
> Done.
Thanks. Few things:
I don't know if the updated repo package with debuginfo is pushed (for rh7).
I just had to manually add the pg15 debuginfo repo.
Also, I think the beta packages should be built with -Og rather than -O2.
cassert will make it slower than debug would make it faster anyway.
Also, I think that postgis32 should be built for pg15. This allows installing
the same package for both old and new postgres versions before doing
pg_upgrade.
> I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also
> wanted to push GeOS 3.11.0 first.
>
> Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as
> well.
>
> Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing
> repository. There is a problem with gdal34 packaging on RHEL 7, and
> I'll push RHEL 7 packages as soon as I (hopefully can) resolve it.
--
Justin
view thread (52+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: postgis for beta releases
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox