Summary: | sys-apps/portage-2.1.2_pre2-r6 reporting non-existant package.mask ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
f5d8fd51ed1e804c9e8d0357e8614e0493b06e96
2006-10-08 14:15:30 UTC
Reopen with 'grep -Rni maven-bin /etc/portage' output. magratea maven-bin # grep -Rni maven-bin /etc/portage /etc/portage/package.mask:1:>dev-java/maven-bin-2 Ok, so this package was intentionally masked by myself - shame on me for forgetting this. The portage message could have been a bit more verbose about the source of that masking. But why in the world I had to remove maven-bin-2.0.2 from my system today? (which was all of a sudden reported to be masked after portage update) It shouldn't even have been installed - as my package.mask says. Was support for /etc/portage/package.mask broken in any recent portage version? User error, closing. Thanks alot for ignoring my question. |