| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: Updating IPC::Run in CI? |
| Date: | 2025-09-22 20:17:09 |
| Message-ID: | CAOYmi+=5sUxPCxC7mVB8B_2k3EdFZ_eOb6khXmtoknuZWTqDGg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 18, 2025 at 12:35 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-09-22 20:24:08 | Re: Updating IPC::Run in CI? |
| Previous Message | Dmitry Koval | 2025-09-22 20:12:20 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |