public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Fetter <[email protected]>
To: [email protected]
Subject: Re: Moving to HTTPS
Date: Sat, 7 Jan 2017 22:01:40 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20buildfarm-members>
On Sat, Jan 07, 2017 at 07:12:07PM -0500, Tom Lane wrote:
> Andrew Dunstan <[email protected]> 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?
You could use install a more modern Perl version just for the
buildfarm client while keeping the system perl marooned however far in
the past we promise to support. Don't know just how painful that is
on those machines...
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
--
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Moving to HTTPS
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox