>>> md5 files ;-) files/blackdown-jre-1.4.2.03
>>> md5 files ;-) files/digest-blackdown-jre-1.4.2.03
>>> md5 files ;-) files/digest-blackdown-jre-1.4.2.03-r2
>>> md5 src_uri ;-) j2re-1.4.2-03-linux-i586.bin
>>> Unpacking source...
>>> Unpacking j2re-1.4.2-03-linux-i586.bin...
>>> Source unpacked.
>>> Test phase [not enabled]: dev-java/blackdown-jre-1.4.2.03
>>> Install blackdown-jre-1.4.2.03 into /var/tmp/portage/blackdown-jre-1.4.2.03/image/ category dev-java
* Creating /var/tmp/portage/blackdown-jre-1.4.2.03/image//opt/blackdown-jre-1.4.2.03/lib/rt.jar
/usr/portage/dev-java/blackdown-jre/blackdown-jre-1.4.2.03.ebuild: line 72: /var/tmp/portage/blackdown-jre-1.4.2.03/image//opt/blackdown-jre-1.4.2.03/lib/unpack: No such file or directory
!!! ERROR: dev-java/blackdown-jre-1.4.2.03 failed.
!!! Function unpack_jars, Line 74, Exitcode 0
!!! Failed to unpack jar files lib/rt.jar.
!!! If you need support, post the topmost build error, NOT this status message.
emerge --info, please...
Created attachment 87268 [details]
emerge --info output
by your command
Huh? What are you trying to do here?
> Portage 2.0.54-r2 (default-linux/x86/2006.0
trying to get software installed?
(In reply to comment #5)
> trying to get software installed?
Yeah, so perhaps sort out which arch are you running on?!
Ah. Found where that came from. I had blindly updated /etc/make.profile on my boxes, and didn't have sufficient caffeination.
Updating make.profile properly, blackdown-jdk is no longer included in emerge -uDp world. Indeed, trying to emerge -p blackdown-jdk and/or blackdown-jre gives me:
!!! All ebuilds that could satisfy "blackdown-jre" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-java/blackdown-jre-1.3.1-r9 (masked by: package.mask, -* keyword)
# Joseph Jezak <email@example.com> (05 Mar 2006)
# Please use IBM's Java instead on PPC
# Masked because there are better options and security issues with this version
- dev-java/blackdown-jre-1.4.2.03 (masked by: -* keyword)
- dev-java/blackdown-jre-1.4.2.03-r2 (masked by: -* keyword)
- dev-java/blackdown-jre-1.4.1-r1 (masked by: -* keyword)
For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
which is totally inappropriate. What's the deal?
java isn't keyworded for ia64, also - your system is completely screwed. Why are you reopening this bug? You should reinstall from scratch.
in what way is the system "completely screwed" praytell?
(In reply to comment #10)
> in what way is the system "completely screwed" praytell?
Apart from your wrong arch set mistake, you've got two glibc versions and two linux-headers versions installed, for good measure.
> virtual/os-headers: 18.104.22.168-r2, 2.6.11-r2
Anyway, there's no Java for ia64, case closed.
url for more information on this, please?
(In reply to comment #12)
> url for more information on this, please?
On what? java use flag is use.masked on ia64 profiles, there's no ia64 keyword for blackdown-jre or anything else either.
# grep java /usr/portage/profiles/default-linux/ia64/use.mask
If you want to try java on ia64, use dev-java/jrockit-jdk-bin.
I meant more information on glibc and linux-headers (and slots, since I thought that these were slotted or something). Particularly, "why two versions of glibc (specifically 2.3.x and 2.4.x) is bad". I should also specify that the arch thing I had going on was a simple fix, as I outlined.
I have emerge -C'ed the old versions (after checking to make sure that nothing important needed them) and things seem fine. I've bumped things up to ~ia64, and am re-emerging things. Things still seem far from "screwed", let alone having to re-install.
Neither of them is slotted. Anyway, this is not a support forum, use forums.g.o. or IRC for such questions.