Is it OK to stabilize =app-crypt/johntheripper-1.7.9-r6 ? If so, please CC all arches which have stable keywords for older versions of this package and add STABLEREQ keyword to the bug.
Adding amd64 and x86 for now. Those work and are reasonably tested. arm has issues that I'm looking into.
In my x86 machine with an intel graphic card, if I want to install =app-crypt/johntheripper-1.7.9-r6[opencl] I need this: =dev-util/intel-ocl-sdk-2.0.31360 But that package it's not keyworded on x86.
(In reply to comment #2) > In my x86 machine with an intel graphic card, if I want to install > =app-crypt/johntheripper-1.7.9-r6[opencl] I need this: > > =dev-util/intel-ocl-sdk-2.0.31360 > > But that package it's not keyworded on x86. Honestly enabling opencl without having an amd/ati card or at least an nvidia card is silly. Intel's opencl performance is significantly worse than standard cpu implementation. (Although at this time the same can be said for all the opencl/cuda stuff in john, it's all pretty early stage). Additionally the intel-ocl-sdk supports intel core versions of processors so all the supported hardware is 64 bit. I'm not sure why the package is keyworded -x86, so I'm adding the maintainer for clarity. Xarthisius, any desire to keyword intel-ocl-sdk for x86?
(In reply to comment #3) > (In reply to comment #2) > > In my x86 machine with an intel graphic card, if I want to install > > =app-crypt/johntheripper-1.7.9-r6[opencl] I need this: > > > > =dev-util/intel-ocl-sdk-2.0.31360 > > > > But that package it's not keyworded on x86. > > > Honestly enabling opencl without having an amd/ati card or at least an > nvidia card is silly. Intel's opencl performance is significantly worse than > standard cpu implementation. (Although at this time the same can be said for > all the opencl/cuda stuff in john, it's all pretty early stage). > > Additionally the intel-ocl-sdk supports intel core versions of processors so > all the supported hardware is 64 bit. I'm not sure why the package is > keyworded -x86, so I'm adding the maintainer for clarity. > > Xarthisius, any desire to keyword intel-ocl-sdk for x86? It cannot be keyworded on x86 due to the simple fact that it's a binary blob that doesn't have (nor will have) 32bit libraries. That's why it has "-x86" in KEYWORDS
(In reply to comment #4) > It cannot be keyworded on x86 due to the simple fact that it's a binary blob > that doesn't have (nor will have) 32bit libraries. That's why it has "-x86" > in KEYWORDS Failsafe for that situation added: + 09 Jan 2013; Kacper Kowalik <xarthisius@gentoo.org> opencl-0-r2.ebuild: + Put nvidia/ati in required_use for x86. Thanks to Vicente Olivert Riera + <peratu@carrosses.com> for report
(In reply to comment #5) > (In reply to comment #4) > > It cannot be keyworded on x86 due to the simple fact that it's a binary blob > > that doesn't have (nor will have) 32bit libraries. That's why it has "-x86" > > in KEYWORDS > > Failsafe for that situation added: > > + 09 Jan 2013; Kacper Kowalik <xarthisius@gentoo.org> opencl-0-r2.ebuild: > + Put nvidia/ati in required_use for x86. Thanks to Vicente Olivert Riera > + <peratu@carrosses.com> for report THANKS! Arch teams please proceed.
amd64 stable
x86 stable. Last arch, closing
arm issues resolved, let's stabilize the rest of the arches TARGETS remaining alpha arm hppa mips ppc ppc64 sparc
still no mips stable keywords.
alpha stable
arm stable
ppc stable
ppc64 stable
Stable for HPPA.
sparc stable. Last arch, closing
