You should emerge everything with *=ibm-jdk-bin-1.6 in jdk.conf and check that it's actually used for most packages while emerging. Lists of stable ebuilds can be generated with https://overlays.gentoo.org/svn/proj/java/scripts/find-stable-java-ebuilds will attach ones here too
Hmm. One thing to consider is that 0.1 should be coming and 0.0 is security vulnerable so might want to wait for 0.1.
Created attachment 149495 [details]
Created attachment 149496 [details]
Created attachment 149497 [details]
Created attachment 149499 [details]
Added testings instructions to our wiki https://overlays.gentoo.org/proj/java/wiki/JDKStabling
(In reply to comment #1)
> Hmm. One thing to consider is that 0.1 should be coming and 0.0 is security
> vulnerable so might want to wait for 0.1.
Any idea when 0.1 can be expected? I've let 0.0 work through your ppc.txt list and found no new problems. So it looks good to go for ppc.
So now we have 126.96.36.199, security fixed.
distfiles as usual (via ssh d.g.o:~caster/tmp)
The question is if we stable now or wait since there was a version bump. Although minor, on amd64 there seem to be larger changes in layout.
Revbumped to fix bugs #220461, #220463, #220467, #220479, #220495, #223575.
*** This bug has been marked as a duplicate of bug 216112 ***
Sorry for the mess.
09 Nov 2009; Markus Meier <email@example.com> ibm-jdk-bin-188.8.131.52.ebuild:
amd64 stable, bug #287490
We go out of here, as a security vulnerability is handled in bug 287490
ibm-jdk-bin has been last-rited and all dependent bugs are closed.