java-config seems to be broken: root@tool xkb # java-config --list-available-vms /usr/bin/java-config: /etc/env.d/java/20*-*: No such file or directory [*-*]
Obviously, you don't have any JREs or JDKs installed. However, the error message is annoying and has to go.
Fixed in dev-java/java-config-0.2.6
root@tool bzd # emerge -s blackdown-jre Searching... [ Results for search key : blackdown-jre ] [ Applications found : 1 ] * dev-java/blackdown-jre Latest version available: 1.3.1-r7 Latest version installed: 1.3.1-r7 Homepage: http://www.blackdown.org Description: Blackdown Java Runtime Environment 1.3.1 root@tool bzd # emerge -s sun-jdk Searching... [ Results for search key : sun-jdk ] [ Applications found : 1 ] * dev-java/sun-jdk Latest version available: 1.4.0-r6 Latest version installed: 1.4.0-r6 Homepage: http://java.sun.com/j2se/1.4/download.html Description: Sun's J2SE Development Kit, version 1.4.0 obviously, java is installed. remerging jre/jdk does not help. i tried java-config-0.2.6, but it only gets rid of error mesg :( reopening.
I'm pretty confident that your problem is a very nasty one and is related to Portage, not java-config. If you upgrade/reinstall a JDK/JRE, all its configuration files will be wiped from /etc/env.d/java. This is _not_ how things are supposed to be, and is a known bug in Portage. What you need to do is: emerge unmerge blackdown-jre emerge blackdown-jre That is first completely unmerge it, then merge it afresh. Sorry for the inconvenience. If this turns out to be the case, you may want to open a new bug against Portage in the hopes that the portage team can fix this sooner rather than later.
