Noticed stuck outdated dev-libs/libxml2 on today's world update: $ emerge -pv1 '>=dev-libs/libxml2-2.9.12' These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/libxml2-2.9.12:2::gentoo [2.9.10-r5:2::gentoo] USE="ipv6 python readline -debug -examples -icu -lzma -static-libs -test -verify-sig%" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_8 python3_9 -python3_7" 0 KiB Total: 1 package (1 upgrade), Size of downloads: 0 KiB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/libxml2:2 (dev-libs/libxml2-2.9.12:2/2::gentoo, ebuild scheduled for merge) USE="ipv6 python readline -debug -examples -icu -lzma -static-libs -test -verify-sig" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_8 python3_9 -python3_7" pulled in by >=dev-libs/libxml2-2.9.12 (Argument) (dev-libs/libxml2-2.9.10-r5:2/2::gentoo, installed) USE="ipv6 python readline -debug -examples -icu -lzma -static-libs -test" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_8 python3_9 -python3_7" pulled in by <dev-libs/libxml2-2.9.12 required by (dev-python/lxml-4.6.3:0/0::gentoo, installed) USE="threads -doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_10 python3_8 python3_9 (-pypy3) -python3_7" ^ ^^^^^^
Please see bug 790737. *** This bug has been marked as a duplicate of bug 790737 ***
(In reply to Thomas Deutschmann from comment #1) > Please see bug 790737. This bug is about resolver ambiguity.(In reply to Thomas Deutschmann from comment #1) > Please see bug 790737. It does not deal with resolver ambiguity.
(In reply to Sergei Trofimovich from comment #2) If you are trying to report a bug to the portage team, please assign it to them.
I do not. I think the upper bounds for popular packages should not conflict with one another to avoid ambiguous final plan. If you disagree it's fine with me. I'll have to maintain local masks.
(In reply to Sergei Trofimovich from comment #4) > I do not. I think the upper bounds for popular packages should not conflict > with one another to avoid ambiguous final plan. I can't follow what you are trying to say here. I don't see any evidence of an actual dependency conflict. dev-python/lxml needs <dev-libs/libxml2-2.9.12. However, you explicitly ran this: emerge -pv1 '>=dev-libs/libxml2-2.9.12' And Portage tells you that is impossible to accomplish. If you were doing a simple @world upgrade, I would expect Portage to emit a warning that it is unable to upgrade libxml2, and continue on as normal.
Did you mean to request that dev-libs/libxml2-2.9.12 be masked? If so, a comment on the other bug will suffice.