-
Bug
-
Resolution: Known Error
-
Normal
-
None
-
None
-
None
When dev-python/cffi is auto-updated via autogen, it creates a dependency problem. This problem isn't related to autogen but to how the dependencies on cffi are written. zstandard contains:
DEPEND="dev-python/cffi:=[${PYTHON_USEDEP}]"
Because of the :=, which will lock it to cffi's sub-slot, and the sub-slot defaulting to PV, this means that when cffi is updated, zstandard will need to be rebuilt. However, we hit the uber-bug in Portage dep resolving where on a world update, if you don't have zstandard in the world set, you get a mess:
I get this:
!!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict:dev-python/cffi:0 (dev-python/cffi-1.14.1:0/1.14.1::python-modules-kit, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (dev-python/cffi-1.14.0:0/1.14.0::python-modules-kit, installed) pulled in by dev-python/cffi:0/1.14.0=[python_targets_python3_7(-),python_targets_python2_7(-),-python_single_target_python3_7(-),-python_single_target_python2_7(-)] required by (dev-python/zstandard-0.14.0:0/0::python-modules-kit, installed) ^^^^^^^^^^ It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously.For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
Workaround would be to remove the := from zstandard. Real fix which I have asked from zmedico for the last year would be to pull things like zstandard into the world set so this dep can be auto-resolved.
