Bug 546036 – virtual/jdk-1.8.0 should be at least unmasked after dev-java/oracle-jdk-bin-1.8.0.40-r1 stabiliation

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description ChaosEngine 2015-04-09 07:50:42 UTC]

Running # emerge --depclean -vp gives unfulfilled dependency:

 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 *
 *   =dev-java/oracle-jdk-bin-1.7.0* pulled in by:
 *     virtual/jdk-1.7.0


Reproducible: Always

Steps to Reproduce:
1. emerge --depclean -vp
Actual Results:  
virtual/jdk-1.7.0 pulls dev-java/oracle-jdk-bin-1.7.0 even when stable dev-java/oracle-jdk-bin-1.8.0.40-r1 is present

Expected Results:  
virtual/jdk-1.8* should pull dev-java/oracle-jdk-bin-1.8* as dependency

[Comment 1 James Le Cuirot 2015-04-09 09:36:09 UTC]

I don't understand what you're saying. Firstly, virtual/jdk-1.8* does pull dev-java/oracle-jdk-bin-1.8* as dependency.

RDEPEND="=dev-java/oracle-jdk-bin-1.8.0*"

Secondly, virtual/jdk-1.7.0 is supposed to pull in dev-java/oracle-jdk-bin-1.7.0 even when stable dev-java/oracle-jdk-bin-1.8.0.40-r1 is present. Both the virtuals and the actual VMs are slotted so you can have 1.7 and 1.8 installed at the same time. If you don't want 1.7 any more then unmerge virtual/jdk:1.7.

[Comment 2 ChaosEngine 2015-04-09 10:05:11 UTC]

Yes, you are right, my Bbad. It must be my bad day, because I haven't checked it from this angle.

What about unmasking virtual/jdk? Will this be happening soon?

[Comment 3 James Le Cuirot 2015-04-09 10:17:03 UTC]

Given that Oracle is currently the only 1.8 JDK we have then yes, I imagine so.