Summary: | trying to emerge multiple masked packeges only reports first one | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Christopher Smith <bugzilla> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | arne_bab, esigra, gentoo-bugs, jsado_sc3, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christopher Smith
2008-03-27 19:56:26 UTC
I think you have a valid request, but generally, it's better practice to use the autounmask program (from the app-portage/autounmask package) to unmask packages instead of overriding ACCEPT_KEYWORDS via the environment. In this case, the actual underlying issue was not a masking problem, but rather treated as a masking problem by portage and resolved in the same way. Specifically, revdep-rebuild can try to emerge specific atoms that no longer exist in the portage tree, and instead of reporting all of the missing ebuilds (which portage treats as having a null keyword), it only reports the first. However, reporting all the masking problems at once will both fix the ~arch issue and the no-ebuild issue. *** Bug 236225 has been marked as a duplicate of this bug. *** *** Bug 253845 has been marked as a duplicate of this bug. *** *** Bug 281185 has been marked as a duplicate of this bug. *** Add depends on 280097 because Zac add it in duplicate bug 281185 Is this bug not resolved by the addition of --autounmask (portage-2.1.9)? Seems to work pretty well for me. *** This bug has been marked as a duplicate of bug 280097 *** |