| Summary: | sys-apps/portage-2.2.18 gives poor reason for keyword changes | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Khumba <bog> |
| Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | ||
| Priority: | Normal | ||
| Version: | 2.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info | ||
*** This bug has been marked as a duplicate of bug 419381 *** |
Created attachment 405812 [details] emerge --info I'm setting up a new amd64 system and installing firefox-38.0.5 which is currently ~amd64. This requires >=dev-libs/nss-3.19 which are also all ~amd64. I added firefox but not nss to package.accept_keywords, and Portage gives me the recommendation: The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by net-misc/networkmanager-1.0.2-r1::gentoo # required by @selected # required by @world (argument) =dev-libs/nss-3.19.1 ~amd64 I have USE=networkmanager, so while there is technically a dependency from networkmanager to nss (underneath firefox even, many layers deep, with emerge -t --unordered-display), it would make more sense if firefox were shown as the depending package, since it's the one forcing the version: # grep -n nss /g/www-client/firefox/firefox-38.0.5.ebuild 61: >=dev-libs/nss-3.19 # grep -n nss /g/net-misc/networkmanager/networkmanager-1.0.2-r1.ebuild 23:kernel_linux +nss +modemmanager ncurses +ppp resolvconf selinux systemd teamd test \ 30: ^^ ( nss gnutls ) 57: nss? ( >=dev-libs/nss-3.11:= ) 169: --with-crypto=$(usex nss nss gnutls) \ I've never noticed Portage not give the correct reason before. Was I just lucky, and this is an approximate explanation?