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

From Jacob Champion
Subject Re: Updating IPC::Run in CI?
Date
Msg-id CAOYmi+nrR0gY=jfVSjoCj134Fn_JODkd0f7=OEgGpAsTvypaKQ@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?
List pgsql-hackers
On Fri, Oct 31, 2025 at 2:40 PM Jacob Champion
<jacob.champion@enterprisedb.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.champion@enterprisedb.com> wrote:
> On Fri, Oct 31, 2025 at 2:55 PM Andres Freund <andres@anarazel.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



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Consistently use the XLogRecPtrIsInvalid() macro
Next
From: Tom Lane
Date:
Subject: Re: Use merge-based matching for MCVs in eqjoinsel