Closed mhworth closed 5 years ago
We removed blis due to a license violation. See https://github.com/conda-forge/cython-blis-feedstock/issues/2. Tried fixing it in https://github.com/conda-forge/cython-blis-feedstock/pull/3, but ran into a different issue.
+1 on this, our builds started failing this AM since spaCy depends on the cython-blis package. Will keep an eye on #3!
Help in fixing the failures in #3 will resolve this issue
Issue: All conda-forge packages are failing to install in fresh install of Anaconda
We have been using a docker-based build and deploy system with Anaconda+conda-forge at it's core for about two years now with no hiccups. Yesterday (after no changes from our side), all of our builds started failing, saying that packages were missing. Now I can't install anything that comes from conda-forge.
This only seems to happen on a fresh installation--I can install things in my environments that were already initialized before, just when I'm starting from scratch it doesn't work.
Nothing at all has changed in our dockerfiles, so I'm not sure what happened. Here is a simple dockerfile that can replicate my issue:
Running
docker build -t test .
with that Dockerfile yields the following:This is the actual output from our build (python incompatibilities seems to be a commonality):
Perhaps something all of the sudden doesn't like python 3.7.3, despite it having worked for months. Maybe something changed in the build process?
Any idea what's happened all of the sudden? Our entire company has ground to a halt over this one, so I'm happy to help however I can to resolve this.
Environment (
conda list
):Details about
conda
and system (conda info
):