Thread

Re: Updating IPC::Run in CI?

Andres Freund <andres@anarazel.de> — 2025-12-17T17:06:31Z

Hi,

On 2025-11-18 09:14:38 -0800, Noah Misch wrote:
> On Tue, Nov 18, 2025 at 08:29:14AM -0800, Jacob Champion wrote:
> > On Mon, Nov 17, 2025 at 12:22 PM Noah Misch <noah@leadboat.com> wrote:
> > > It's a CPAN-managed key.  See if the key here gives what you need:
> > > http://pgpkeys.eu/pks/lookup?search=071B468507812067912B951258FDA3CBB759E5C4&fingerprint=on&op=index
> > 
> > It does, thanks, though I was surprised to see that I had to override
> > Module::Signature's defaults to get it to be used. gpg.conf was
> > ignored. So shouldn't Module::Signature default to a keyserver that
> > CPAN actually uses...?
> 
> Yes, Module::Signature should do that, or the key should be on more
> keyservers, or both.  More keyservers would always be a good thing anyway for
> such a prominent key.
> 
> > > If it helps, you don't actually need to run an installation process on
> > > IPC::Run.  You can just unpack the tarball and add $PWD/IPC-Run/lib to the
> > > PERL5LIB envar.
> > 
> > I can't quite decide whether that would make things easier or harder.
> > The CPAN approach has been a lot of yak shaving, but once it works, it
> > should hopefully work the same across all the platforms...
> 
> Yep.  Whichever works better for you.

A quick ping on this thread, triggered a by a few related spurious cfbot
failures:

https://cirrus-ci.com/task/4697674038902784
https://cirrus-ci.com/task/6272264783527936

Are you stuck on anything right now, or just busy otherwise?

Greetings,

Andres Freund