Summary: | emerge being not very helpful with slot conflicts caused by new USE-flags | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kirill Elagin <kirelagin> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kirill Elagin
2014-03-12 09:40:33 UTC
> So, It seems to me that emerge should be more straightforward,
> because when you see something [like
> this](http://pastie.org/pastes/8910914/text) it's difficult
> to tell, what's really going on, and which slot conflict to blame. Even guys
> at #gentoo
> (one of them being a developer) coundn't do that.
If all conflicts are of the "no parents that aren't satisfied by other packages in this slot" type and there are no blockers, then it most likely hit the backtrack limit. Increasing the --backtrack value as emerge suggest should help in this case.
Anyway, the result with the current portage-9999 should already be better.
|