| Summary: | OVERLAY+METADATA | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Maurizio Disimino <h3y> |
| Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | carpaski, mholzer |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Ok... This isn't a bug. You aren't unmasking the package, so it's not considered. Just because you have it installed doesn't mean it is available to portage. |
Portage .38 here. beryllium net-fs # emerge -s nfs-utils Searching... [ Results for search key : nfs-utils ] [ Applications found : 1 ] * net-fs/nfs-utils Latest version available: 0.3.3-r1 Latest version installed: 1.0.1 Homepage: http://nfs.sourceforge.net/ Description: kernel NFS client and server daemons Well, I've just installed nfs-utils-1.0.1 with the following command: # ACCEPT_KEYWORDS="~x86" emerge -u nfs-utils Moreover, note that the ${DESCRIPTION} belongs to the 0.3.3-r1 ebuild. Same behavior with portage .39. However, I also have the nfs-utils-1.0.1.ebuild in $PORTDIR_OVERLAY. Maurizio