Re: Updating IPC::Run in CI?

Jacob Champion <jacob.champion@enterprisedb.com>

From: Jacob Champion <jacob.champion@enterprisedb.com>

To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>

Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Noah Misch <noah@leadboat.com>

Date: 2025-09-22T22:35:22Z

Lists: pgsql-hackers

On Mon, Sep 22, 2025 at 1:24 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> +1.  Maybe we can stop doing this at some future time when all those
> OSes have absorbed an up-to-date IPC::Run, but for the near term we're
> merely exposing ourselves to known failures.

On Mon, Sep 22, 2025 at 1:27 PM Andres Freund <andres@anarazel.de> wrote:
> I think your position has merit. However, I'd like to have at least one of the
> tasks continue to use the non-built-in IPC::Run.
>
> I'll review patches installing a newer IPC::Run.

I will work on that, then. Thanks both!

> Seperately, I wonder if we ought to add a warning to configure/meson output
> about IPC::Run < 2025...

Probably. I imagine it's going to be very noisy for a bit, though.

--Jacob