dependency.bad 1 app-admin/conky/conky-1.9.0-r2.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-power/apcupsd']
Patrick -- What change did you want me to make? Looks like conky is keyworded ~arm and so is the apcupsd ebuild I'm currently working with, the latest conky needs a patch before enabling the apcupsd use flag..however that patch is for conky and not apcupsd...I'll let the conky maintainer decide how he wants to handle it. Are you suggesting I block simultaneous installation until I know of a conky ebuild with the patch applied?
As far as I can tell repoman tripped over the situation where no arm-keyworded apcupsd ebuild is visible. (Maybe an unexpected entry in package.mask ? I haven't checked, but this error was visible on two machines with a clean checkout) The last change was in the apcupsd ebuilds, so I deduced that this change caused the error to appear. If I'm wrong then I apologize for causing confusion :)
The selinux ebuild for apcupsd seems to be masked in some places....do you have selinux enabled? Also, on powerppc, the conky package is masked when apcups use flag is enabled. I didn't haven't seen any issue specific to arm.
You accidentally removed the few versions that had arm keywords. Repoman complains: dependency.bad 2 app-admin/conky/conky-1.9.0-r2.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-power/apcupsd'] app-admin/conky/conky-1.9.0-r3.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-power/apcupsd'] sys-power/apcupsd $ grep KEY * apcupsd-3.14.10-r5.ebuild:KEYWORDS="~amd64 ~x86 ~ppc ~x86-fbsd" And: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-power/apcupsd/apcupsd-3.14.10-r1.ebuild?hideattic=0&view=markup KEYWORDS="~amd64 ~arm ~ppc ~x86 ~x86-fbsd" looking at profiles: arch/alpha/use.mask:apcupsd arch/powerpc/ppc64/64ul/package.use.mask:app-admin/conky apcupsd So - please either mask the useflag, or restore old / re-keyword new versions of apcupsd for arm.
~arm added to 3.14.10-r5, in cvs - this ebuild will become the new stable on all arches if there are no significant bugs.
*** Bug 489320 has been marked as a duplicate of this bug. ***