Summary: | sys-apps/portage: emerge -uD @world slot conflict involving virtual/dist-kernel | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mgorny, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=771183 https://bugs.gentoo.org/show_bug.cgi?id=778038 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Zac Medico
2021-05-24 02:12:13 UTC
A larger --backtrack value solved it, which probably also goes for bug 771183 since nobody every responded to my question about backtracking in bug 771183 comment 10, It looks like the original emerge output is indicating binpkg use? I seem to hit this bug when world updating with `-k --with-bdeps=y` while dropping either of these options succeeds, so I guess that might point to `-k` as a trigger for this. (In reply to John Helmert III from comment #2) > It looks like the original emerge output is indicating binpkg use? I seem to > hit this bug when world updating with `-k --with-bdeps=y` while dropping > either of these options succeeds, so I guess that might point to `-k` as a > trigger for this. This might be bug 778038 (too?). *** This bug has been marked as a duplicate of bug 778038 *** |