When a KEYWORD of "~arch" is in /usr/portage and a KEYWORD of "arch" is in PORTAGE_OVERLAY, the "~arch" KEYWORD is used. This is wrong because datas from PORTAGE_OVERLAY should have priority on everything. Reproducible: Always Steps to Reproduce: 1.copy ebuild with ~arch keyword into local overlay 2.change ~arch to arch in overlay 3.emerge -s the application with ACCEPT_KEYWORDS="arch" Actual Results: It will not list the app as available because ~arch KEYWORD from main tree overrides the local PORTAGE_OVERLAY Expected Results: It should list the app as available because "arch" KEYWORD is set in overlay This problem exists since /var/cache/edb/dep is created and used. I guess when emerge creates that dependency database it only uses values from /usr/portage and ignores the overlay data. !!! This bug was previously opened but accidently marked as dupe !!!
Has been fixed a long time ago