release candidate mm patches should not be apart of the stable release. I've ran into two separate buggy kernels because of rc's and i've searched bugzilla and found many others running into problems. Reproducible: Always Steps to Reproduce: 1. emerge -pv mm-sources 2. 3. Actual Results: if a release candidate is the latest release, it will show up Expected Results: only final releases show up without the ACCEPT_KEYWORDS=~arch
You're right. The ebuilds have been marked as unstable.
looks like lostlogic isn't aware of this bug # grep KEYWORD /usr/portage/sys-kernel/mm-sources/mm-sources-2.6.6_rc1-r1.ebuild KEYWORDS="x86 ~amd64 ~ia64 -*" # grep Header /usr/portage/sys-kernel/mm-sources/mm-sources-2.6.6_rc1-r1.ebuild # $Header: /home/cvsroot/gentoo-x86/sys-kernel/mm-sources/mm-sources-2.6.6_rc1-r1.ebuild,v 1.1 2004/04/19 21:21:15 lostlogic Exp $
Fixed again. Ebuild updated and commited.
However, now there are no unmasked mm-sources (~arch) in portage which breaks emerge updates for several things. Currently I have to modify ebuilds to update with ati-drivers: root@nemo ckdake # emerge -p mm-sources ati-drivers These are the packages that I would merge, in order: Calculating dependencies !!! all ebuilds that could satisfy "mm-sources" have been masked. !!! possible candidates are: - sys-kernel/mm-sources-2.6.6_rc1-r1 (masked by: -* keyword) - sys-kernel/mm-sources-2.6.6-r2 (masked by: -* keyword) - sys-kernel/mm-sources-2.6.6-r4 (masked by: -* keyword) - sys-kernel/mm-sources-2.6.6-r1 (masked by: -* keyword) - sys-kernel/mm-sources-2.6.6_rc3-r1 (masked by: -* keyword) - sys-kernel/mm-sources-2.6.6_rc2-r1 (masked by: -* keyword) !!! Error calculating dependencies. Please correct.
See: ttp://bugs.gentoo.org/show_bug.cgi?id=51046
