Needed by genkernel-next Thanks!
Any problem with CCing arches? (is the only blocker for genkernel-next ;)) Thanks :)
Apologies, I thought I'd already done this; apparently didn't hit SaveChanges.. CC'ing arches: ~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86 (note, i don't recall what we're supposed to do about alpha and sparc, but since both profiles don't list ~arch in their default ACCEPT_KEYWORDS i figured it is still relevant to CC them here)
Thanks a lot Ian
amd64 stable
x86 stable
ppc stable
ppc64 stable
ia64 stable
Looks like this now depends on bugs 498092 498094 due extra USE flags :/
+ 18 Jan 2014; Pacho Ramos <pacho@gentoo.org> dmraid-1.0.0_rc16-r3.ebuild: + ia64 stable, bug #487672 (thanks to Emeric Maschino for testing) +
klibc fails tests on alpha (see bug 516172), dietlibc doesn't even build (bug 516174). In both cases, I doubt it will ever be fixed, so we'll probably just mask the USE flags and dekeyword the packages. glibc can't even consistently produce a working libc implementation, so I doubt these two projects ever will. I'll give the other bugs a week or two and the go ahead with the USE-mask.
I would go with USE mask directly (I don't think dietlibc will be fixed in that week)
(In reply to Pacho Ramos from comment #12) > I would go with USE mask directly (I don't think dietlibc will be fixed in > that week) That week was mostly so people could point out if I was doing something wrong with testing. And to let me deal with other bugs that are more likely to yield results :-/
Stable on alpha.
sparc stable
actually no, needs dev-libs/klibc stable...i don't feel confident about it. Readding sparc
(In reply to Raúl Porcel from comment #16) > actually no, needs dev-libs/klibc stable...i don't feel confident about it. > Readding sparc I suggest you simply mask, either package.use.mask or package.use.stable.mask, USE="klibc" and proceed accordingly
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
An automated check of this bug failed - repoman reported dependency errors: > dependency.bad sys-fs/dmraid/dmraid-1.0.0_rc16-r3.ebuild: DEPEND: arm(default/linux/arm/13.0) ['dev-libs/klibc', 'dev-libs/dietlibc'] > dependency.bad sys-fs/dmraid/dmraid-1.0.0_rc16-r3.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['dev-libs/klibc', 'dev-libs/dietlibc']
[master 71a5ccb] profiles/arch/arm/package.use.stable.mask: mask dietlibc and klibc USEs as they won't go to stable 1 file changed, 4 insertions(+)
arm stable, closing.