Portmaster failing
@lbutlr
kremels at kreme.com
Wed Jan 1 20:51:43 UTC 2020
On 01 Jan 2020, at 13:46, Franco Fichtner <franco at lastsummer.de> wrote:
>
>
>
>> On 1. Jan 2020, at 9:42 PM, @lbutlr <kremels at kreme.com> wrote:
>>
>> On 01 Jan 2020, at 13:40, Franco Fichtner <franco at lastsummer.de> wrote:
>>> security/openssl was removed before, now security/openssl111 has become security/openssl.
>>
>> Ugh.
>>
>>> A bit too eager for my taste, but that's why we all have private trees, don't we. ;)
>>
>> This is going to go poorly, if previous attempts to update to 1.1 are any indication.
>
> With PHP 5.6 axed prematurely a while back I am interested to see OpenSSL 1.0.2
> phased out now with a number of ports still not supporting 1.1.1 and seeing them
> marked as broken sooner or later.
Well, at this point I cannot install openssl111 without deinstalling openssl, which I cannot deinstall since it is gone from ports.
Looks like I have to remove openssl, which … I mean, seriously, this seems pretty hostile.
Name : openssl
Version : 1.0.2u,1
Installed on : Sun Dec 22 08:13:27 2019 MST
There was nothing at all on the 22nd about “WARNING THIS WILL BREAK EVERYTHING IN A WEEK” which to mean seems like it should have been made super obvious.
--
There are 10 types of people in the world: Those who understand
binary and those who don’t.
More information about the freebsd-ports
mailing list