Bug 16778 – Core Portage-tree KEYWORDS override the ones in PORTDIR_OVERLAY

• Product: Portage Development
• Status: RESOLVED DUPLICATE

[Description Christian Birchinger (RETIRED) 2003-03-03 19:15:40 UTC]

KEYWORDS in the core portage-tree are overriging own packages in PORTDIR_OVERLAY
if both package versions have the same version. This behaviour is new an wrong
with the latest portage releases.

Example:
~ $ grep ^KEYWORDS
/usr/portage/sys-kernel/sparc-sources/sparc-sources-2.4.20-r4.ebuild
KEYWORDS="~x86 -ppc ~sparc"

~ $ grep ^KEYWORDS
/usr/local/portage/sys-kernel/sparc-sources/sparc-sources-2.4.20-r4.ebuild 
KEYWORDS="~x86 -ppc sparc"

# emerge -up world

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild    U ] sys-kernel/sparc-sources-2.4.20-r3 [2.4.20-r4] 


This problem apeard with 2.0.47 of portage. Early revisions at least didn't
overwrite the /var/cache/edb/dep/sys-kernel/sparc-sources-2.4.20-r4 on rsync
update. So it was possible to fix it at least manualy there. That ability is
now gone as well.

The ebuilds in PORTDIR_OVERLAY should really have priority on this things.
If you disagree with that make it at least optional.

Many people i know move some unstable ebuild to their local overlay and only
adust the KEYWORDS so they don't have to do ACCEPT_KEYWORD on the fly which
causes lots of problems on a rebuild or emerge -e world etc. Having the KEYWORDS
stable in the users own PORTDIR_OVERLAY has advantages over on the fly accepting
keywords.

Reproducible: Always
Steps to Reproduce:
Described in "Details"
Actual Results:  
It wants to downgrade the ebuild because core portage tree has a unstable
KEYWORDS= and it ignores the stable KEYWORDS= in local overlay

Expected Results:  
It should see that own overlay has KEYWORDS= stable and the local overlay should
have priority. (also in dep cache generating)

[Comment 1 SpanKY 2003-03-03 23:23:17 UTC]

*** This bug has been marked as a duplicate of 16540 ***