Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQ3MH-0005dO-KT for buildfarm-members@arkaria.postgresql.org; Sun, 08 Jan 2017 02:37:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cQ3MG-0006Ep-Vz for buildfarm-members@arkaria.postgresql.org; Sun, 08 Jan 2017 02:37:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cQ3MG-0006Ej-PP for buildfarm-members@postgresql.org; Sun, 08 Jan 2017 02:37:20 +0000 Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cQ3MC-0006x4-IZ for buildfarm-members@postgresql.org; Sun, 08 Jan 2017 02:37:19 +0000 Received: by mail-qk0-x233.google.com with SMTP id a20so111890396qkc.1 for ; Sat, 07 Jan 2017 18:37:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Lv2FvbTOzJKqPcS/01RMHoC30ev9PvWVM5puJ7wllJw=; b=Bt8FTMbO1E+OSQh8Eroksql2Uo8LW8A3rZxbPtHw4LjqT3IHTpxmga+j2NKr1f0uvQ 1O7XA9OZImkc17nE4fqkpMoimdAEAq7KCDHZUJhy8iHSFzy4Z6Gi7SanR8qalseyYtN2 ubbjTW0z7mutefXvomab88Kea7ml8ZmuMgnoWezyku7Aje48X0G5muN4B+JFeNVMhYhb 2wzq8rliOPzViTxQKJV8sM43F5qPmPj3e0PvHpBqPxLd5MD0cDRRJd39zyxXG1sSAaYT c58a766uAgsNNJkxkzE8DBLtpKXwRVy9STGWMHltx5AtTCAhIP2028BYsWHtcv1n3Lrk ipkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Lv2FvbTOzJKqPcS/01RMHoC30ev9PvWVM5puJ7wllJw=; b=g5F3qVsaQ+Uf/ZltTfB/F55sqvU1urUfL/oX/O0X/G87b3X0qMOsZq9kbqH6QTOTt+ hwDcsYmB1JoZWnEapOHNCThwrWqc5asp7GUYVY285UYjt3mfAad6MAa3+X/j8R042sh1 avYuVFZ/KKjHAVeU3Talmu5D+mCEfBFGLcEVmxISRs6axf9BHf7LqfuAPB5rj8wy/iAz s1spbpuKQ2qZWPO4+17wcZXKJlWAqvwgwrk+Ld70OYU2P0vSfJnFbn7j2ySUi9ODDl/a XBvAms7BSP57GpxXmQGFwe2oBgE74DWRj7KznBVByDRdbrxa4f5vK4FF4ITkhYrDEh5R rGQQ== X-Gm-Message-State: AIkVDXJN1hk228Z8/c0zJvJQYCvpkKQlPNXayvrVUIZXOjQN1GHwCqU0Ftt3U5D/DUed/dPP X-Received: by 10.55.97.75 with SMTP id v72mr89175853qkb.80.1483843034582; Sat, 07 Jan 2017 18:37:14 -0800 (PST) Received: from [192.168.10.146] ([98.122.164.227]) by smtp.gmail.com with ESMTPSA id x40sm53937929qtx.12.2017.01.07.18.37.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Jan 2017 18:37:13 -0800 (PST) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: Moving to HTTPS To: Tom Lane References: <89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net> <20170107215523.GA294152@tornado.leadboat.com> <96080bc2-086f-c47f-6cee-b7f00a9bcd38@2ndQuadrant.com> <3104.1483834327@sss.pgh.pa.us> Cc: buildfarm-members@postgresql.org, buildfarm-admins@postgresql.org Message-ID: Date: Sat, 7 Jan 2017 21:37:12 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <3104.1483834327@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: buildfarm-members Precedence: bulk Sender: buildfarm-members-owner@postgresql.org On 01/07/2017 07:12 PM, Tom Lane wrote: > Andrew Dunstan 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 -- Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/buildfarm-members