Packages listed in '/etc/portage/packages.accept_keywords' show incorrect keywords in 'equery list -pm'. For example, an installed package 'pack_examp' which has keyword '~amd64' and is listed in package.accept_keywords with 'pack_examp ~amd64' will show the following result in 'equery list pack_examp' [IP-] [ ] pack_examp Expected behavior is to still show the correct keyword, such as [IP-] [ ~] pack_examp A similar behavior happens for masked packages which are listed in packages.unmask. These packages do not show up in 'equery list' as being masked packages. I am not sure if this is intended behavior. I can understand how the portage system may treat this packages as no longer having the unstable keyword or no longer being masked since the user has exempted them through the appropriate package.* file. However, it would be useful to know for these package what the current state of the package is in the portage tree. I am using the following portage and toolkit versions: sys-apps/portage-2.2.14:0 app-portage/gentoolkit-0.3.0.9-r2:0
It is working as designed. What you are seeing actually is the current state of the package because you have either unmasked the package or accepted the keyword. What you actually want is a mechanism to disable using the settings in /etc/portage when outputting the information and I will need to look at the Portage API to see how feasible being able to do that would be. Leaving the bug open for now until we can determine if this is a feasible enhancement to make.
(In reply to Paul Varner from comment #1) > It is working as designed. > thanks for looking into this. i guess as i use equery I am just expecting to see the true keyword status. the "I" flag tells me something is installed. if it has a "~" keyword then I know somewhere the keyword has been accepted, but i still get to know that the package is considered unstable.
