Re: [buildfarm-members] Moving to HTTPS
От | Andrew Dunstan |
---|---|
Тема | Re: [buildfarm-members] Moving to HTTPS |
Дата | |
Msg-id | a04ba257-712f-b47e-54bd-a2ee1087f014@2ndQuadrant.com обсуждение исходный текст |
Ответ на | Re: [buildfarm-members] Moving to HTTPS (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [buildfarm-members] Moving to HTTPS
Re: [buildfarm-members] Moving to HTTPS |
Список | buildfarm-members |
On 01/07/2017 07:12 PM, Tom Lane wrote: > Andrew Dunstan <andrew.dunstan@2ndquadrant.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
В списке buildfarm-members по дате отправления: