Re: Updating IPC::Run in CI?

Jacob Champion <jacob.champion@enterprisedb.com>

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

To: Nazir Bilal Yavuz <byavuz81@gmail.com>

Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Noah Misch <noah@leadboat.com>

Date: 2025-09-22T20:17:09Z

Lists: 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