Summary: | dev-python/lxml stable requires outdated <dev-libs/libxml2-2.9.12 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergei Trofimovich (RETIRED) <slyfox> |
Component: | Current packages | Assignee: | Sam James <sam> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | base-system |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergei Trofimovich (RETIRED)
2021-05-19 18:53:35 UTC
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. |