Closed cpaulik closed 8 years ago
@cpaulik I am reluctant to over-specify dependency to workaround other issues but we can take a PR to fix that if nothing works.
By other issues I mean this: pygrib
depends on ecmwf_grib
→ jasper
→ jpeg
and, from all of those, only jpeg
exists on defaults
. Note that jasper
, which brings jpeg
into the equation, is properly pinned to jpeg 9*
. So, IMO, conda is not respecting that pin and is installing a broken jasper
there. Breaking also ecmwf_grib
and pygrib
.
I do know that conda had a few improvements some time ago. They added the channel preference featire to alleviate some of those issues. Can you check if you have the latest conda and add the conda-forge
channel on top of defaults
in your .condarc
? Maybe that solves it...
Note also that if you specify pygrib
at first conda will do the right thing (conda create -n test-pygrib python=3.5 pygrib
).
I'm using conda 4.1.11
which is the latest release.
Moving the conda-forge channel before the defaults channel works.
But you are right that this is a conda problem. Running conda install -c conda-forge jasper
correctly updates jpeg
while jpeg
as a second level dependency is not updated.
But you are right that this is a conda problem
The channel preference alleviates the problem but, IMO, it does not really fixes it. Conda should update jpeg
or at least refuse to install pygrib
in your original scenario.