From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | buildfarm-members(at)postgresql(dot)org, buildfarm-admins(at)postgresql(dot)org |
Subject: | Re: Moving to HTTPS |
Date: | 2017-01-08 02:37:12 |
Message-ID: | a04ba257-712f-b47e-54bd-a2ee1087f014@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
On 01/07/2017 07:12 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>> Yeah, you're right. Or perhaps even more simply we could do:
>> perl -MLWP::Simple -e 'print qq{BAD\n} unless head(q{https://www.postgresql.org});'
> Hmm, so that reports BAD on all four of my buildfarm critters :-(.
>
> On longfin, which is running a current macOS release, "cpan install
> LWP::Protocol::https" seems to be enough to fix it; but on the other
> three, I get various flavors of failure. It looks like the root cause is
> that the versions of the relevant modules that are currently available
> from CPAN assume newer versions of OpenSSL and/or other Perl modules than
> these machines have installed.
>
> I could embark on a massive update binge, but that would sort of defeat
> the purpose of testing against old Perl versions. Thoughts?
>
Ugh. I was afraid of something like that. We might need to look at
providing a proxy or something.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2017-01-08 06:01:40 | Re: Moving to HTTPS |
Previous Message | Tom Lane | 2017-01-08 00:12:07 | Re: Moving to HTTPS |