Yes, the problem should be caused by having 1.6.0 already installed. I ran
into a similar problem recently. This is a JAva, not a JPackage issue. Java
versions can coexist on the same machine but must be installed in order.
You can install 1.6.x on a machine running 1.5.x but you cannot install
1.5.x on a machine with 1.6.x. The only workaround I found is to uninstall
1.6.x and resintall both.
Michel
--On mercredi 16 janvier 2008 10:38 +0100 Steve Traylen
<[EMAIL PROTECTED]> wrote:
On Jan 16, 2008, at 10:37 AM, Eva Myers wrote:
On Tue, Jan 15, 2008 at 10:31:58AM -0800, Tony Hoffmann wrote:
Last night's update of my SL4 based machines showed machines with the
java-1.4.2-sun-compat package having jdk-1.5.0 and java-1.5.0-sun-
compat
installed as a dependency. Checking java-1.4.2-sun-compat does show
java-1.5.0-sun-compat as being a requirement. Why is that?
I have a related problem - my yum updates are failing with the message
Error: Missing Dependency: jdk = 2000:1.5.0_14-fcs is needed by
package
+java-1.5.0-sun-compat
The problem seems to be that I have a newer version of the JDK (1.6.0)
installed locally. Is there any way to work around this problem
without uninstalling the new JDK?
I'm beginning to sound like a stuck record here.
The JPackage packages of java coexist perfectly.
Eva.
--
Steve Traylen
[EMAIL PROTECTED]
*************************************************************
* Michel Jouvin Email : [EMAIL PROTECTED] *
* LAL / CNRS Tel : +33 1 64468932 *
* B.P. 34 Fax : +33 1 69079404 *
* 91898 Orsay Cedex *
* France *
*************************************************************
