curl 7.71.1 _3 broken on osx about curl-feedstock HOT 10 CLOSED

xref.: conda-forge/admin-requests#98

from curl-feedstock.

One of the more annoying parts of this is what happens to conda:

>conda update --all  
Collecting package metadata (current_repodata.json): failed

CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://repo.anaconda.com/pkgs/main/osx-64/current_repodata.json>
Elapsed: -

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.

If your current network has https://www.anaconda.com blocked, please file
a support request with your network engineering team.

'https://repo.anaconda.com/pkgs/main/osx-64'

Also @ocefpaf, should this really be closed?

from curl-feedstock.

_3 is not broken. It's just that upgrading from _2 to _3 will result in a broken environment. Can't do anything except tell users to do conda install libssh2 --force-reinstall

from curl-feedstock.

Except once _3 is installed, conda is non-functional. This is in my base environment--this update bricks my entire conda install.

from curl-feedstock.

Issue is that once _2 is installed, you'll not be able to update the environment ever.

from curl-feedstock.

If I do:

conda install --offline --force-reinstall libssh2

it then complains about libssl.1.1.dylib missing.

from curl-feedstock.

You need force reinstall openssl too

from curl-feedstock.

And krb5 it turns out (libgssapi_krb5.2.2.dylib).

So for posterity, my full fix was essentially:

conda install --offline --force-reinstall libssh2 openssl krb5

from curl-feedstock.

I am really sorry @dopplershift :/

from curl-feedstock.

No worries, I was more concerned about anyone else who ended up in that boat (e.g. users I might need to support on my end) but looks like I got the problematic _2 over the weekend so probably not a lot of others who will hit this. Fixing a busted env is just another day that ends in "y" for me 😆

from curl-feedstock.