Summary: | sys-apps/portage: There are no sets to satisfy 'foo' message does not display the origin of the broken package set reference | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Frank Hollenbach <frank.hollenbach> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 144480 |
Description
Frank Hollenbach
2008-11-06 23:07:29 UTC
Did you change anything before this started happening? Perhaps you've corrupted the EMERGE_DEFAULT_OPTS variable somehow. Please post the output of this command: portageq envvar EMERGE_DEFAULT_OPTS Actually, I think it's more likely that the problem is in /var/lib/portage/world_sets. Have you got anything in there? We can improve the display_missing_pkg_set function to show where the broken package set reference originates. I could originate from the command line, /var/lib/portage/world_sets, /etc/portage/sets, a user-defined set in /etc/portage/sets.conf, or a set defined by an overlay. |