From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
cc: buildfarm-members@postgresql.org, buildfarm-admins@postgresql.org
Subject: Re: Moving to HTTPS
In-reply-to: <96080bc2-086f-c47f-6cee-b7f00a9bcd38@2ndQuadrant.com>
References: <89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net>
 <20170107215523.GA294152@tornado.leadboat.com>
 <96080bc2-086f-c47f-6cee-b7f00a9bcd38@2ndQuadrant.com>
Comments: In-reply-to Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
	message dated "Sat, 07 Jan 2017 17:08:01 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3103.1483834327.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 07 Jan 2017 19:12:07 -0500
Message-ID: <3104.1483834327@sss.pgh.pa.us>
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org

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.pos=
tgresql.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?

			regards, tom lane


--=20
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members