Summary: | emerge world doesn't always give full information as to why a package is blocked | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alan McKinnon <alan.mckinnon> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723 |
Description
Alan McKinnon
2007-06-28 07:50:02 UTC
This is similar to bug 174509. I consider this one invalid, the downgrade notification should be warning enough to check things. Can't make emerge explain every possible situation in detail, that attempt would end in a huge if-elif mess. Or what specific conditions should trigger the "higher version is masked by" notification you request? Zac, I don't quite see the relation to bug 174509. We already have a notification if a different version is selected, we even have a whole column in the status display dedicated to it. (In reply to comment #2) > I consider this one invalid, the downgrade notification should be warning > enough to check things. Can't make emerge explain every possible situation in > detail, that attempt would end in a huge if-elif mess. Or what specific > conditions should trigger the "higher version is masked by" notification you > request? OK, I see what you are getting at. The circumstance that triggered the block is quite rare, so it probably is better to just leave things as they are. |