Summary: | Existing packages not considered to satisfy dependencies | ||
---|---|---|---|
Product: | Portage Development | Reporter: | M. Creidieki Crouch <creidieki+gentoobugs> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
M. Creidieki Crouch
2004-03-23 18:09:48 UTC
unmask those packages in /etc/portage/packages.keywords I hadn't realized that there was a file for unmasking specific packages. That would invalidate the bug, as I have it written. The file /etc/portage/packages.keywords doesn't actually exist on my system, though, nor do any other files named "packages.keywords". The /etc/portage directory is empty. Do you know if it's kept somewhere else in recent versions of portage? "emerge -p portage" tells me " [ebuild R ] sys-apps/portage-2.0.50-r1 " Thanks. /etc/portage doesnt exist because you didnt make it `man 5 portage` |