If I go to sun site url listed to pick up 1.4.1_01, I find 1.4.1_02 instead. It would be nice if the dependency was on 1.4.1_X. Reproducible: Always Steps to Reproduce: 1.emerge portagemaster 2.follow directions to pick up sun 1.4.1_01 jdk 3.at sun URL find 1.4.1_02 instead, and placing that in the same spot as is recommended for 1.4.1_01 fails Actual Results: emerge stops with error re need to download 1.4.1_01 from sun site Expected Results: ideally ebuild would have proceeded with the more recent version of 1.4.1 ln -s the new to the old name fails copying the new to the old name fails I'm going to go digging on sun site for old version
I cannot reproduce this; what happens is that portagemaster is set to depend on the most recent (stable, unless you do USE="~x86") JDK available in the tree. I suspect your problem is that at the time you reported this (sorry for the insane delay), we did not have an updated ebuild for the 1.4.0 JDK. This is a known, continual problem with the binary releases from Sun, which we cannot do anything about. We always play catchup when they release a new version, as they remove the old one, and we're not allowed to mirror.