On May 4, 2016, at 8:58 AM, Ryan Schmidt wrote:
>> Can you just manually put the openssl distfile on the master mirror? Since
>> so many ports depend on it, we're likely to see lots of noise from people
>> with older systems.
>
> Done.
Excellent. Thanks Ryan!
--
Daniel J. Luke
_
> On May 4, 2016, at 7:50 AM, Daniel J. Luke wrote:
>
> On May 4, 2016, at 8:48 AM, Ryan Schmidt wrote:
>>> If we can force a mirror of openssl in the meantime (if it's not there
>>> already), it would be useful to prevent more tickets from being opened for
>>> failed builds.
>>
>> The mirro
On May 4, 2016, at 8:48 AM, Ryan Schmidt wrote:
>> If we can force a mirror of openssl in the meantime (if it's not there
>> already), it would be useful to prevent more tickets from being opened for
>> failed builds.
>
> The mirror-all-ports script runs automatically twice a week. The script t
On May 4, 2016, at 7:47 AM, Daniel J. Luke wrote:
> On May 4, 2016, at 8:46 AM, Ryan Schmidt wrote:
>> On May 4, 2016, at 1:58 AM, Joshua Root wrote:
>>> Probably the best fix on our end would be to reinstate the immediate
>>> mirroring that used to happen from a post-commit hook. And possibly
On May 4, 2016, at 8:46 AM, Ryan Schmidt wrote:
> On May 4, 2016, at 1:58 AM, Joshua Root wrote:
>> Probably the best fix on our end would be to reinstate the immediate
>> mirroring that used to happen from a post-commit hook. And possibly make the
>> build block until the mirroring is done. In
On May 4, 2016, at 1:58 AM, Joshua Root wrote:
> Probably the best fix on our end would be to reinstate the immediate
> mirroring that used to happen from a post-commit hook. And possibly make the
> build block until the mirroring is done. In fact, maybe the mirroring could
> be triggered from
Yeah. Unfortunately there are rather a lot of not-that-old systems and
devices out there that can't use 1.1. But, also unfortunately, version
1.0 is pretty broken.
Probably the best fix on our end would be to reinstate the immediate
mirroring that used to happen from a post-commit hook. And po
This is probably caused by the site now requiring TLS 1.1 or better:
https://www.ssllabs.com/ssltest/analyze.html?d=openssl.org&s=194.97.150.234
Since PCI compliance is requiring the phasing out of TLS 1.0 support, this is
probably going to become much more common in the near future (PCI require
It looks like the snowleopard and mtln buildbots can't download current openssl:
DEBUG: Fetching distfile failed: Unknown SSL protocol error in connection to
www.openssl.org:443
Is it time to retire the buildbots for these old OS versions? Should we set
them up to use the squid proxy I host fo
