| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-18 16:29:14 |
| Message-ID: | CAOYmi+=roEb2txm4Zj383awyJh_-XY8S1Oyb06t7EZr99QQxOQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 17, 2025 at 12:22 PM Noah Misch <noah(at)leadboat(dot)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...?
> 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...
Thanks,
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-11-18 16:33:57 | Re: postgresql.conf.sample tab width |
| Previous Message | ocean_li_996 | 2025-11-18 16:26:19 | Re: minor improvement in snapbuild: use existing interface and removefake code |