conda install does not resolve pinned transitive dependencies

[kynan]

Consider the following scenario: my conda env already has package A at version x. I conda install D, which depends on C, which depends on B, which depends on A pinned at version y > x. There is no conflict of A version y with any other package.

conda install D does not upgrade A, leaving D in a broken state.

My concrete example involves packages on conda-forge (which I believe should not make a difference) and the packages in question are: magics dependens on python-eccodes depends on jasper depends on jpeg 9.*. The Azure notebooks root env provides jpeg 8d. conda install -y -c conda-forge magics does not upgrade jpeg.

This is using conda 4.3.22 on python 2.7. Azure notebooks currently provides the Anaconda 4.10 package set with some Azure specific extras.

[kynan]

Here's a notebook demonstrating the issue

[kalefranz]

Probably of interest to @mcg1969

[mcg1969]

The version of jasper that is being pulled in is jasper-1.900.1-1. This version does not specify a version of jpeg. See here. Conda is doing the right thing here.

Now, the latest build of jasper, jasper-1.900-4, does indeed specify a version of jpeg. See here. But conda is not required to pull the latest build of a package. And indeed, it can't, because it can't upgrade the version of jpeg to do so. So it chooses the latest version of the package that is compatible with the underlying environment, and that's build 1.

This is, I'm afraid, a hotfixing issue. Conda-forge needs to remove or hotfix older builds of 1900.1

[kalefranz]

This is, I'm afraid, a hotfixing issue. Conda-forge needs to remove or hotfix older builds of 1900.1

[github-actions]

Hi there, thank you for your contribution to Conda!

This issue has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue if needed.