dependency.bad 10 net-fs/samba/samba-3.6.9.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.9.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.12.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.12.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.13.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.13.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.14.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.14.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.14-r1.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi'] net-fs/samba/samba-3.6.14-r1.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['sys-apps/dmapi']
looks like the dmapi clean up accidentally dropped the ebuilds w/arm in them
(In reply to comment #1) > looks like the dmapi clean up accidentally dropped the ebuilds w/arm in them Oops, my mistake. Was there any reason why arm wasn't added to 2.2.12 when it was bumped?
(In reply to comment #2) not really. probably my fault.