Re: Updating IPC::Run in CI? - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Updating IPC::Run in CI?
Date
Msg-id CAOYmi+=5sUxPCxC7mVB8B_2k3EdFZ_eOb6khXmtoknuZWTqDGg@mail.gmail.com
Whole thread Raw
In response to Re: Updating IPC::Run in CI?  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Updating IPC::Run in CI?
Re: Updating IPC::Run in CI?
List pgsql-hackers
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?

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: Dmitry Koval
Date:
Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Next
From: Tom Lane
Date:
Subject: Re: Updating IPC::Run in CI?