Summary: | portage requires me to unmask dev-libs/glib-2.32.4 for packages that don't need it | ||
---|---|---|---|
Product: | Portage Development | Reporter: | kipplasterjoe |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
kipplasterjoe
2012-08-22 18:06:10 UTC
If you can reproduce the problem then please attach a debug log, created as follows: emerge -avuDN world --debug &> debug.log I solved a part of the problem by running "emerge -avuDNt world", x11-misc/lightdm was unmasked on my system and requires dev-libs/glib-2.32.4. Now I did a downgrade to stable lightdm and no longer have the problem. I think portage should display only packages actually triggering the unmask request. At the moment it says: The following keyword changes are necessary to proceed: #required by net-libs/farsight2-0.0.29, required by net-im/pidgin-2.10.6[gstreamer], required by @selected, required by @world (argument) =dev-libs/glib-2.32.4 ~amd64 but it means: The following keyword changes are necessary to proceed: #required by x11-misc/lightdm-1.3.2, required by @selected, required by @world (argument) =dev-libs/glib-2.32.4 ~amd64 This is a problem, the user doesn't now which package is responsible for requiring dev-libs/glib-2.32.4. (In reply to comment #2) > I think portage should display only packages actually triggering the unmask > request. Yes, that seems like a case of bug 419381. *** This bug has been marked as a duplicate of bug 419381 *** |