My system is an arm64 on Pi400. equery m cpuid * sys-apps/cpuid [gentoo] Maintainer: conikost@gentoo.org (Conrad Kostecki) Upstream: None specified Homepage: http://www.etallen.com/cpuid.html Location: /var/db/repos/gentoo/sys-apps/cpuid Keywords: 20220224:0: amd64 x86 License: GPL-2+ grep cpuid /etc/portage/package.accept_keywords sys-apps/cpuid ~* pi400 ~ # emerge -vp sys-apps/cpuid These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "sys-apps/cpuid" have been masked. !!! One of the following masked packages is required to complete your request: - sys-apps/cpuid-20220224::gentoo (masked by: missing keyword) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. pi400 ~ # vi /etc/portage/package.accept_keywords pi400 ~ # grep cpuid /etc/portage/package.accept_keywords sys-apps/cpuid * pi400 ~ # emerge -vp sys-apps/cpuid These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N *] sys-apps/cpuid-20220224::gentoo 128 KiB Total: 1 package (1 new), Size of downloads: 128 KiB sam_ stated in the chat, that ~* includes *. Imho the often used documentation below isn't exact. It lacks the detail that the more stable/more selective options are included. > In addition to the normal values from ACCEPT_KEYWORDS, package.accept_keywords supports three special tokens[1]: > > * — Package is visible if it is stable on any architecture. > ~* — Package is visible if it is in testing on any architecture. > ** — Package is always visible (KEYWORDS are ignored completely). > > The last choice is useful for live package versions (e.g. SVN/Git/Mercurial package versions) because live ebuilds don't have a KEYWORDS variable. Reproducible: Always
It's surprising if it's intended given we normally work off of "visibility" and stable packages are visible in ~arch.
Since it was explained in the chat I extended https://wiki.gentoo.org/wiki/ACCEPT_KEYWORDS with Note The behaviour of ~arch and ~* differ: ~arch includes arch, ~* doesn't include *. If you want to use the most recent version of a package which is marked stable or unstable on any architecture then you need to specify "* ~*".
