Re: Updating IPC::Run in CI?

Hi,

On 2025-09-22 13:17:09 -0700, Jacob Champion wrote:
> On Thu, Sep 18, 2025 at 12:35 PM Jacob Champion
> <jacob.champion@enterprisedb.com> wrote:
> > Right. On the Debian side, looks like bookworm is stuck on 20220807.0
> > -- and updating to trixie won't help us either; that just gets us up
> > to 20231003.0.
> 
> To more explicitly defend my position here: I can request updates from
> package maintainers for <insert OS here>, but if the end result is
> that our LTS distributions will still be lagging, there's not much
> point. I'd rather bake the latest IPC::Run into our CI, and I'm happy
> to contribute code and cycles towards that.
> 
>  Any other opinions?

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.

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

Greetings,

Andres Freund