Should dev-java/icedtea-bin be pulled as a dependency after emerging dev-java/sun-jre-bin? Here's what I have: emerge sun-jre-bin These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-java/java-config-wrapper-0.16 0 kB [ebuild N ] dev-java/java-config-2.1.11-r3 0 kB [ebuild N f ] dev-java/sun-jre-bin-1.6.0.31 USE="alsa nsplugin -X -jce" 0 kB [ebuild N ] virtual/jre-1.6.0 0 kB (...) emerge -uDNtp world These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild U ] sys-auth/pam_mount-2.13::local [2.12::gentoo] USE="ssl -crypt (-selinux)" 0 kB [nomerge ] virtual/jdk-1.7.0 [nomerge ] dev-java/icedtea-bin-7.2.0-r2 USE="X alsa cups nsplugin -cjk -doc -examples -source" [nomerge ] dev-java/java-config-2.1.11-r3 [ebuild NS ] virtual/jre-1.7.0 [1.6.0] 0 kB [ebuild N ] virtual/jdk-1.7.0 0 kB [ebuild N ] dev-java/icedtea-bin-7.2.0-r2 USE="X alsa cups nsplugin -cjk -doc -examples -source" 0 kB Reproducible: Always Steps to Reproduce: 1. emerge sun-jre-bin 2. emerge -uDN 3. watch your terminal
If you install virtual/jre-1.6.0 and virtual/jre-1.7.0 isn't masked, Portage will try to upgrade the virtual. jre:1.7 will then pull in one of oracle-jre-bin:1.7 oracle-jdk-bin:1.7, icedtea:7 or icedtea-bin:7 and as oracle-jre-bin is fetch-restricted settle for icedtea-bin. Either mask (don't accept ~arch) the virtual/jre-1.7.0 or install a provider explicitly, ie. emerge -1 oracle-jre-bin. Not a bug but the expected behaviour.