This is not so much a bug as an issue to be aware of. For a full background, please see the following forum thread: http://forums.gentoo.org/viewtopic-t-533905.html Basically I'm using an amd64 host to build a gentoo system for an arm target. My problem is that module-init-tools-3.2.2-r2 has a DEPEND ">=sys-apps/baselayout-1.12.7-r2". As this is a DEPEND, not a RDEPEND, portage uses the build host's configuration to resolve the dependency. I run ACCEPT_KEYWORDS="amd64" on my build host. Sadly there are no unmasked baselayout packages for amd64 which will satisfy module-init-tools-3.2.2-r2's DEPEND. The result is that when I run emerge, I get dependency errors about packages "masked by: ~amd64 keyword", which was very confusing as I was emerging packages for an arm target. Please review this dependency. I realize the module-init-tools ebuild runs a script (generate-modprobe.conf) which is in baselayout, so the DEPEND is correct (baselayout is needed for module-init-tools to compile). however, should this script really be in baselayout, or should it be included with module-init-tools instead? Is it really necessary to have such a recent (masked for most arch's) baselayout as a DEPEND? I have solved my particular problem by hard-masking module-init-tools-3.2.2-r2. I guess ultimately the problem will disappear when a more recent version of baselayout gets unmasked for amd64 (perhaps for the 2007.0 profile?) Please forgive me for posting this on bugzilla and feel free to close it immediately if you know baselayout-1.12.7-r2 is absolutely required. I just wanted to make you aware of the issue. Cheers! Reproducible: Always
There's nothing to fix here; ~arch package depending on ~arch package is not a bug.
