Please stabilize dev-java/icedtea-6.1.10.1 on amd64 All bugs that are still open in #247140 seem to be solved or are not relevant for amd64.
(In reply to comment #0) > All bugs that are still open in #247140 seem to be solved or are not relevant > for amd64. Yeah but it would mean stabilizing also icedtea-web which has bug 363049.
It's time to bit the bullet. Please stabilize per summary. I believe there's not much testing needed (e.g. emerging all java packages) at this point. Default USE flags are enough. Please don't enable cacao, jamvm, zero. Testing browser plugin (icedtea-web) can be done by selecting it with eselect java-nsplugin and then restarting e.g. firefox and googling for some applets. In case of emerge dependency issues, emerge icedtea6-bin first for bootstrap. I hope that's all, thanks.
amd64: all emerges ok
Created attachment 285669 [details] circular deps I got circular deps problem in my (pretty much minimal) stable chroot. Cant tell more, haven't slept much lately. Ideas?
Tomas, easy, simply emerge the jdk by itself first, that should be enough, if not the xalan by itself. Other will follow
Hm if emerging icedtea6-bin first didn't help with the circular deps, then emerging also virtual/jdk should. Please tell me if it's really the case, as that needs to be added to docs.
*** Bug 366427 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > Tomas, > > easy, simply emerge the jdk by itself first, that should be enough, if not the > xalan by itself. Other will follow I had to emerge xalan first, simple "emerge =dev-java/icedtea-6.1.10.3" nor "dev-java/icedtea-web-1.1.1", didnt do. Then it emerged fine.
*** Bug 366425 has been marked as a duplicate of this bug. ***
Please re-add us when the blockers bugs are fixed. Thanks.
we move to 6.1.10.4 now, please clear old vulnerable version.
Gonna restate this a bit later after changing VMHANDLE.
OK. No we are on 6.1.11.2. Can we stabilize this in the next weeks?
Given bug 421031 maybe a bump to 6.1.11.3 should be done first?
So can we stabilize as 6.1.11.3 is in?
(In reply to comment #4) > Created attachment 285669 [details] > circular deps > > I got circular deps problem in my (pretty much minimal) stable chroot. Cant > tell more, haven't slept much lately. Ideas? This is the same as in Bug 382421 . I just had circular dependencies with ant-core, the same as in Bug #415139 but using icedtea-6.1.11.3. From the comments in the other bugs "portage needs some assistance to get icedtea bootstrapped".
USE="-nsplugin -webstart -jbootstrap -nss -alsa -source" emerge -avu icedtea disables all but the X use flag, yet I still get: (dev-java/icedtea-7.2.4.1::gentoo. ebuild scheduled for merge) depends on (dev_java/icedtea-7.2.4.1::gentoo, ebuild scheduled for merge) (buildtime) which comes up as a circular dependency. How can a product depend on itself? I have virtual/jdk & icedtea-bin installed. This is a new system, but I have finished installing almost every other product, including KDE.
(In reply to Daiajo Tibdixious from comment #17) > USE="-nsplugin -webstart -jbootstrap -nss -alsa -source" emerge -avu icedtea > disables all but the X use flag, yet I still get: > (dev-java/icedtea-7.2.4.1::gentoo. ebuild scheduled for merge) depends on > (dev_java/icedtea-7.2.4.1::gentoo, ebuild scheduled for merge) (buildtime) > > which comes up as a circular dependency. How can a product depend on itself? > > I have virtual/jdk & icedtea-bin installed. > > This is a new system, but I have finished installing almost every other > product, including KDE. Try to USE="jbootstrap"
Removing icedtea-web from this request as of version 1.4.0 icedtea-web supports switching JVM and therefore can be stabilized prior to icedtea.
Are bugs 356991 380745 then only ones blocking this?
Updated summary to reflect current version of 6 in need of stabilisation.
I'm not sure why 356991 & 380745 are blocking this. While I can see the case for allowing users to override the CFLAGS and LDFLAGS used, I can also see it leading to a lot of breakage if JDKs are suddenly being built with compiler flags that no-one has ever tested before.
Obsoleted by Bug 483018 (1.6 JDKs/JREs cleanup).