Although below is an example with emul-linux-x86-java I think I saw the same with both and IBM and Oracle java's already. Emerge just fails unless the downloaded *.bin files are executable. That is because ebuild calls sh /usr/portage/distfiles/jre-*.bin to unpack the sources. Funny. >>> Emerging (1 of 1) app-emulation/emul-linux-x86-java-1.6.0.45 * jre-6u45-linux-i586.bin SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... sh: /mnt/1TB/var/tmp/portage/app-emulation/emul-linux-x86-java-1.6.0.45/distdir/jre-6u45-linux-i586.bin: Permission denied * ERROR: app-emulation/emul-linux-x86-java-1.6.0.45::gentoo failed (unpack phase): * Failed to unpack * * Call stack: * ebuild.sh, line 93: Called src_unpack * environment, line 2687: Called die * The specific snippet of code: * sh "${DISTDIR}"/${A} -noregister || die "Failed to unpack" * * If you need support, post the output of `emerge --info '=app-emulation/emul-linux-x86-java-1.6.0.45::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/emul-linux-x86-java-1.6.0.45::gentoo'`. * The complete build log is located at '/mnt/1TB/var/tmp/portage/app-emulation/emul-linux-x86-java-1.6.0.45/temp/build.log'. * The ebuild environment file is located at '/mnt/1TB/var/tmp/portage/app-emulation/emul-linux-x86-java-1.6.0.45/temp/environment'. * Working directory: '/mnt/1TB/var/tmp/portage/app-emulation/emul-linux-x86-java-1.6.0.45/work' * S: '/mnt/1TB/var/tmp/portage/app-emulation/emul-linux-x86-java-1.6.0.45/work/jre1.6.0_45'
Well, the java emul set is done and maintained by java team entirely :/
(In reply to Pacho Ramos from comment #1) > Well, the java emul set is done and maintained by java team entirely :/ No idea about that; but if it is so, please update the metadata to reflect that.
+ 18 Oct 2013; Pacho Ramos <pacho@gentoo.org> metadata.xml: + This case is special: java emul package is entirely handled by java team + Done :)
emul-linux-x86-java has been removed from the tree.
