Closed akrherz closed 5 years ago
Argh :-(
Looking into this... Hold on!
Edit: the culprit is descartes
, not sure why yet. Looking into it...
Editing again: the problem is actually matplotlib b/c all the stack was migrated to the new openssl except qt, a matplotlib dependency. xref.: https://github.com/conda-forge/qt-feedstock/pull/98
I'll see what was wrong with the gdal=2.4.0
builds and see if I can get them back and/or rebuild gdal=2.4.1 with the old openssl
too.
Wow @ocefpaf , your support and effort is amazing. thank you so much.
If you unpin gdal or use conda create -n gdal python=3.6 gdal=2.4.0 geopandas
it should work now. Basically I got the gdal 2.4.0 with the old openssl back. As soon as we fix https://github.com/conda-forge/qt-feedstock/pull/98 this issue will go away in "the right way" and you will be able to install gdal=2.4.1
. Sorry about that. Qt is the hardest package we have in our stack and it is taking too long to build it. Unfortunately it blocks matplotlib
and ends up affecting a lot of other packages b/c of that.
Thank you, I was able to update my full env again and have a working GDAL 2.4.0
Issue: I can't install geopandas with gdal=2.4.1 on linux64 for python 3.6.
My current "production" env is having trouble getting re-created and/or upgraded and not hit apparently broken gdal=2.4.0 builds in conda-forge. I am trying to resolve why there is a logjam that is not permitting me to use gdal=2.4.1, which appears to work. Thanks as always.