After a complete reinstall, it appears the blackdown-jre ebuild has been broken. It downloads properly, but doesn't copy or install anything properly, as well, the symbolic link for the mozilla plugin is wrong. Worked a few months ago, but anyone trying to install Gentoo now will get a non-working Java run-time environment: bash-2.05a# emerge blackdown-jre Calculating dependencies ...done! >>> emerge dev-java/blackdown-jre-1.3.1-r7 to / >>> md5 ;-) j2re-1.3.1-FCS-linux-i386.tar.bz2 >>> Unpacking source... >>> Source unpacked. >>> Install blackdown-jre-1.3.1-r7 into /var/tmp/portage/blackdown-jre-1.3.1-r7/image/ category dev-java cp: cannot stat `/var/tmp/portage/blackdown-jre-1.3.1-r7/work/j2re1.3.1/bin': No such file or directory cp: cannot stat `/var/tmp/portage/blackdown-jre-1.3.1-r7/work/j2re1.3.1/lib': No such file or directory cp: cannot stat `/var/tmp/portage/blackdown-jre-1.3.1-r7/work/j2re1.3.1/man': No such file or directory cp: cannot stat `/var/tmp/portage/blackdown-jre-1.3.1- r7/work/j2re1.3.1/plugin': No such file or directory /usr/lib/portage/bin/dodoc: COPYRIGHT does not exist. /usr/lib/portage/bin/dodoc: README does not exist. /usr/lib/portage/bin/dodoc: INSTALL does not exist. mv: cannot stat `/var/tmp/portage/blackdown-jre-1.3.1-r7/image//opt/blackdown- jre-1.3.1/lib/font.properties': No such file or directory /usr/sbin/ebuild.sh: /var/tmp/portage/blackdown-jre-1.3.1- r7/image//opt/blackdown-jre-1.3.1/lib/font.properties.orig: No such file or directory rm: cannot remove `/var/tmp/portage/blackdown-jre-1.3.1- r7/image//opt/blackdown-jre-1.3.1/lib/font.properties.orig': No such file or directory strip: >>> Completed installing into /var/tmp/portage/blackdown-jre-1.3.1-r7/image/ >>> Merging dev-java/blackdown-jre-1.3.1-r7 to / --- /opt/ >>> /opt/blackdown-jre-1.3.1/ --- /usr/ --- /usr/share/ --- /usr/share/doc/ >>> /usr/share/doc/blackdown-jre-1.3.1-r7/ >>> /usr/share/doc/blackdown-jre-1.3.1-r7/LICENSE.gz --- /usr/lib/ --- /usr/lib/mozilla/ --- /usr/lib/mozilla/plugins/ --- /etc/ --- /etc/env.d/ >>> /etc/env.d/java/ >>> /etc/env.d/java/20blackdown-jre-1.3.1 >>> /usr/lib/mozilla/plugins/javaplugin_oji.so -> /opt/blackdown-jre-1.3.1/plugi n//mozilla/javaplugin_oji.so * No default VM found, setting blackdown-jre-1.3.1 as default Now using Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1) >>> Regenerating /etc/ld.so.cache... >>> dev-java/blackdown-jre-1.3.1-r7 merged. >>> Recording dev-java/blackdown-jre in "world" favorites file... * GNU info directory index is up-to-date. * IMPORTANT: 1 config files in /etc need updating. * Type emerge --help config to learn how to update config files.
Yes, I have found the same problem myself. Portage downloads index.html and j2re-1.3.1-FCS-linux-* from whatever mirror your use, then fails to unpack the tgbz2, and then installs an empty /opt/blackdown-jre. The "fix" is to fallback to the /usr/portage/dev-java/blackdown-jre that is distributed on the 1.2 ISO. Whoever broke this should be slapped around with a live trout. (whatever the environmentalists might say) The worst of it, is that that portage-current shows blackdown-jre-1.3.1-r7... The same as is distributed with 1.2. Hope someone with CVS commit falls back to the stable version.
Now it installs fine, but the mozilla plugin symbolic link seems to not be generated properly on my machine. Last thing the ebuild does is: >>> /usr/lib/mozilla/plugins/javaplugin_oji.so -> /opt/blackdown-jre-1.3.1/plugin//mozilla/javaplugin_oji.so However between the /'s in ...plugin//mozilla... it should place ${PLATFORM}, but mine is being generate blank. Since this is a fresh 1.2 install, anyone trying to install 1.2 will still get a broken java-vm in Mozilla.
Whooops. Major oversight.
