Closed dwhswenson closed 3 years ago
Locally, conda defaulted to pulling in the newer version (1.5.4) which does not show this issue. But for whatever reason, the OpenPathSampling migration build pulled in 1.5.3. I know can always pin
netcdf4!=1.5.3
in my recipe, but can this be fixed upstream?
A pypy install should pull 1.5.4 b/c that is the only version we built with pypy. Pinning !=1.5.3 is a workaround but that should not be part of the solve there b/c there is no 1.5.3 for pyp :-/
Looks like this is a bug in conda's solver. Pinging @isuruf for awareness.
Should be fixed in an hour or so. See https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/100
Issue: Conda can pull in a version of netCDF4 that doesn't seem to be built for PyPy.
For context, I came across this in https://github.com/conda-forge/openpathsampling-feedstock/pull/5, but I was able to reproduce this issue locally with the following:
Locally, conda defaulted to pulling in the newer version (1.5.4) which does not show this issue. But for whatever reason, the OpenPathSampling migration build pulled in 1.5.3. I know can always pin
netcdf4!=1.5.3
in my recipe, but can this be fixed upstream?Environment (
conda list
):Details about
conda
and system (conda info
):