Re: Updating IPC::Run in CI?

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Updating IPC::Run in CI?
Date: 2025-11-17 18:13:30
Message-ID: CAOYmi+nrR0gY=jfVSjoCj134Fn_JODkd0f7=OEgGpAsTvypaKQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 31, 2025 at 2:40 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> I even considered pulling the tarball straight from Github and
> hardcoding the shasum for it

(For anyone who tries this in the future: Github's source tarballs
don't appear to be stable over time.)

On Fri, Oct 31, 2025 at 3:54 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> On Fri, Oct 31, 2025 at 2:55 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > msys '(echo; echo o conf recommends_policy 0; echo notest install IPC::Run) | cpan'
>
> Heh. Okay, I'll give a version of that a shot.

The echo chain (plus additions) works, but I've gotten stuck at
signature verification:

https://cpan.org/authors/id/N/NJ/NJM/CHECKSUMS
gpg: Signature made Sun Aug 10 02:52:29 2025 UTC
gpg: using RSA key 071B468507812067912B951258FDA3CBB759E5C4
gpg: requesting key 58FDA3CBB759E5C4 from hkp://keyserver.ubuntu.com:11371
gpg: Can't check signature: No public key

Noah, do you know if that's a quick fix on the publishing side?

Thanks,
--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-11-17 18:30:13 Re: Use merge-based matching for MCVs in eqjoinsel
Previous Message Bertrand Drouvot 2025-11-17 17:39:37 Re: Consistently use the XLogRecPtrIsInvalid() macro