Summary: | emerge -uDNpv claims media-gfx/pngrewrite is keyword-masked, while it is not | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 216231 |
Description
Dennis Schridde
2008-06-10 15:37:05 UTC
It seems like the ~amd64 keyword is missing from /var/db/pkg/media-gfx/pngrewrite-1.2.1/KEYWORDS. Does that file contain any keywords? Here are some possible workarounds: 1) echo "=media-gfx/pngrewrite-1.2.1 **" >> /etc/portage/package.keywords 2) rebuild pngrewrite host ~ # cat /var/db/pkg/media-gfx/pngrewrite-1.2.1/KEYWORDS ppc sparc x86 So that message is thrown when I install a package while it is keyword-unmasked, and then remove that keyword-unmasking? Even if the ebuild itself in the tree now contains the keyword? I removed "... **" from package.keywords, when the ebuild got ~amd64 keyworded, because I assumed it was now unneeded. I suppose we can suppress the warning in cases when an available package has keywords. What is the policy on this: Is it allowed to change packages without revision increment while in unstable? One could argue that stable users would never have installed the old package, "self-pwned"? If that is the case (I did not think about this before), it would be useful to have a warning, possibly with a notice: "The tree ebuild is not masked, try reemerging." Otherwise suppression sounds good. Well, suppression is the best option for me because it helps me to avoid more bug reports like this one. :) This is fixed in 2.1.5.5. |