Hi Mario,
On Wed, 12 Nov 2008, Mario Reale wrote:
I had observed the same problem while installing other pS services on FC9.
The only option I had found to still use the repositories was the simultaneous
yum install of the <ps package name> and jdk - after having added the
jpackage repository to the yum repo config files.
( in order to make Java accessible via YUM).
For example:
yum install geant2-java-xml-ls-1.3-1.noarch jdk-1.5.0_16
java-1.5.0-sun-compat tomcat5-webapps tomcat5-admin-webapps
That is funny, when I checked I noticed that java-1.5.0-gcj was already
installed, but the development libraries are not. Running
yum install ps-mdm-flowsa-ma java-1.5.0-gcj-devel
solves the problem. Now I'm not sure anymore that this is a problem in the
perfSONAR rpm's rather then in one of the Fedora 9 rpm's.
But to fix things as you suggest would be ideal. If you scan through the
yum failed install log lines, which is the first update/install
transaction requiring java-1.6.0-sun-compat ? Hans Trompert wrote:
From the messages it is not clear to me which package requires
java-1.6.0-sun-compat. The complete log looks like this:
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
* updates-newkey: ftp.stw-bonn.de
* fedora: ftp.klid.dk
* updates: ftp.klid.dk
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package ps-mdm-flowsa-ma.noarch 0:1.0-1 set to be updated
--> Processing Dependency: tomcat5 for package: ps-mdm-flowsa-ma
--> Processing Dependency: nfdump for package: ps-mdm-flowsa-ma
--> Running transaction check
---> Package tomcat5.i386 0:5.5.27-0jpp.2.fc9 set to be updated
--> Processing Dependency: tomcat5-server-lib = 5.5.27-0jpp.2.fc9 for package: tomcat5
--> Processing Dependency: tomcat5-common-lib = 5.5.27-0jpp.2.fc9 for package: tomcat5
--> Processing Dependency: tomcat5-common-lib = 5.5.27-0jpp.2.fc9 for package: tomcat5
--> Processing Dependency: tomcat5-server-lib = 5.5.27-0jpp.2.fc9 for package: tomcat5
--> Processing Dependency: jakarta-commons-daemon >= 1.0.1 for package: tomcat5
--> Processing Dependency: xerces-j2 >= 2.7.1 for package: tomcat5
--> Processing Dependency: xml-commons-apis >= 1.3 for package: tomcat5
--> Processing Dependency: java-devel >= 1.4.2 for package: tomcat5
--> Processing Dependency: jakarta-commons-io >= 1.2 for package: tomcat5
--> Processing Dependency: xml-commons-apis >= 1.3 for package: tomcat5
--> Processing Dependency: jakarta-commons-launcher >= 0.9 for package: tomcat5
--> Processing Dependency: jakarta-commons-dbcp-tomcat5 for package: tomcat5
--> Processing Dependency: jakarta-commons-collections-tomcat5 for package: tomcat5
--> Processing Dependency: jakarta-commons-pool-tomcat5 for package: tomcat5
---> Package nfdump.i386 0:1.5.7-1 set to be updated
--> Running transaction check
---> Package java-1.6.0-sun-compat.i586 0:1.6.0.06-1jpp set to be updated
--> Processing Dependency: jdk = 2000:1.6.0_06-fcs for package: java-1.6.0-sun-compat
---> Package tomcat5-server-lib.i386 0:5.5.27-0jpp.2.fc9 set to be updated
--> Processing Dependency: tomcat5-jasper = 5.5.27-0jpp.2.fc9 for package: tomcat5-server-lib
--> Processing Dependency: tomcat5-jasper = 5.5.27-0jpp.2.fc9 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-modeler >= 2.0 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-modeler >= 2.0 for package: tomcat5-server-lib
---> Package jakarta-commons-collections-tomcat5.i386 0:3.2-2jpp.2.fc9 set to be updated
---> Package jakarta-commons-daemon.i386 1:1.0.1-6jpp.5.fc9 set to be updated
---> Package xml-commons-apis.i386 0:1.3.04-1jpp.1.fc9 set to be updated
---> Package jakarta-commons-launcher.i386 0:1.1-2jpp.3.fc9 set to be updated
---> Package jakarta-commons-pool-tomcat5.i386 0:1.3-10jpp.3.fc9 set to be updated
---> Package jakarta-commons-dbcp-tomcat5.i386 0:1.2.1-11jpp.3.fc9 set to be updated
---> Package xerces-j2.i386 0:2.7.1-10jpp.1.fc9 set to be updated
--> Processing Dependency: xml-commons-resolver >= 1.1 for package: xerces-j2
---> Package tomcat5-common-lib.i386 0:5.5.27-0jpp.2.fc9 set to be updated
--> Processing Dependency: tomcat5-jsp-2.0-api = 5.5.27-0jpp.2.fc9 for package: tomcat5-common-lib
--> Processing Dependency: tomcat5-servlet-2.4-api = 5.5.27-0jpp.2.fc9 for package: tomcat5-common-lib
--> Processing Dependency: tomcat5-jsp-2.0-api = 5.5.27-0jpp.2.fc9 for package: tomcat5-common-lib
--> Processing Dependency: tomcat5-servlet-2.4-api = 5.5.27-0jpp.2.fc9 for package: tomcat5-common-lib
--> Processing Dependency: jakarta-commons-el >= 1.0 for package: tomcat5-common-lib
--> Processing Dependency: eclipse-ecj >= 3.1.1 for package: tomcat5-common-lib
--> Processing Dependency: eclipse-ecj >= 3.1.1 for package: tomcat5-common-lib
--> Processing Dependency: jakarta-commons-el >= 1.0 for package: tomcat5-common-lib
---> Package jakarta-commons-io.noarch 0:1.3.2-1jpp.1.fc9 set to be updated
--> Running transaction check
---> Package java-1.6.0-sun-compat.i586 0:1.6.0.06-1jpp set to be updated
--> Processing Dependency: jdk = 2000:1.6.0_06-fcs for package: java-1.6.0-sun-compat
---> Package eclipse-ecj.i386 1:3.3.2-12.fc9 set to be updated
---> Package tomcat5-jsp-2.0-api.i386 0:5.5.27-0jpp.2.fc9 set to be updated
---> Package tomcat5-jasper.i386 0:5.5.27-0jpp.2.fc9 set to be updated
---> Package xml-commons-resolver.i386 0:1.1-1jpp.12 set to be updated
---> Package jakarta-commons-modeler.i386 0:2.0-4jpp.2.fc9 set to be updated
--> Processing Dependency: jakarta-commons-logging >= 1.0 for package: jakarta-commons-modeler
--> Processing Dependency: jakarta-commons-collections >= 2.0 for package: jakarta-commons-modeler
--> Processing Dependency: jakarta-commons-beanutils >= 1.3 for package: jakarta-commons-modeler
--> Processing Dependency: jakarta-commons-digester >= 1.2 for package: jakarta-commons-modeler
--> Processing Dependency: jmxri for package: jakarta-commons-modeler
--> Processing Dependency: jaxp_transform_impl for package: jakarta-commons-modeler
---> Package jakarta-commons-el.i386 0:1.0-9jpp.2.fc9 set to be updated
---> Package tomcat5-servlet-2.4-api.i386 0:5.5.27-0jpp.2.fc9 set to be updated
--> Running transaction check
---> Package xalan-j2.i386 0:2.7.0-7jpp.2.fc9 set to be updated
---> Package java-1.6.0-sun-compat.i586 0:1.6.0.06-1jpp set to be updated
--> Processing Dependency: jdk = 2000:1.6.0_06-fcs for package: java-1.6.0-sun-compat
---> Package jakarta-commons-beanutils.i386 0:1.7.0-6jpp.1 set to be updated
---> Package jakarta-commons-collections.i386 0:3.2-2jpp.2.fc9 set to be updated
---> Package jakarta-commons-logging.i386 0:1.0.4-7jpp.5.fc9 set to be updated
---> Package mx4j.i386 1:3.0.1-6jpp.4 set to be updated
--> Processing Dependency: bcel >= 5.0 for package: mx4j
--> Processing Dependency: javamail >= 1.2-5jpp for package: mx4j
--> Processing Dependency: axis >= 1.1 for package: mx4j
--> Processing Dependency: log4j >= 1.2.7 for package: mx4j
--> Processing Dependency: jaf for package: mx4j
---> Package jakarta-commons-digester.i386 0:1.7-7jpp.2 set to be updated
--> Running transaction check
---> Package java-1.6.0-sun-compat.i586 0:1.6.0.06-1jpp set to be updated
--> Processing Dependency: jdk = 2000:1.6.0_06-fcs for package: java-1.6.0-sun-compat
---> Package axis.i386 0:1.2.1-3jpp.8.fc9 set to be updated
--> Processing Dependency: jakarta-commons-discovery for package: axis
--> Processing Dependency: wsdl4j for package: axis
--> Processing Dependency: jakarta-commons-httpclient for package: axis
---> Package classpathx-mail.i386 0:1.1.1-5jpp.3 set to be updated
---> Package bcel.i386 0:5.2-4jpp.2.fc9 set to be updated
--> Processing Dependency: regexp for package: bcel
---> Package log4j.i386 0:1.2.14-4jpp.1.fc9 set to be updated
---> Package classpathx-jaf.i386 0:1.0-11jpp.1.fc9 set to be updated
--> Running transaction check
---> Package regexp.i386 0:1.5-2jpp.1.fc9 set to be updated
---> Package wsdl4j.i386 0:1.5.2-5jpp.2.fc9 set to be updated
---> Package jakarta-commons-httpclient.i386 1:3.1-0jpp.1.fc9 set to be updated
---> Package java-1.6.0-sun-compat.i586 0:1.6.0.06-1jpp set to be updated
--> Processing Dependency: jdk = 2000:1.6.0_06-fcs for package: java-1.6.0-sun-compat
---> Package jakarta-commons-discovery.i386 1:0.4-3jpp.1.fc9 set to be updated
--> Finished Dependency Resolution
java-1.6.0-sun-compat-1.6.0.06-1jpp.i586 from perfsonar-i386 has depsolving problems
--> Missing Dependency: jdk = 2000:1.6.0_06-fcs is needed by package java-1.6.0-sun-compat-1.6.0.06-1jpp.i586 (perfsonar-i386)
What do you think?
Cheers,
HansT.
Hi,
I was trying to install the ps-mdm-flowsa-ma from downloads.perfsonar.eu
with yum on a cleanly installed Fedora 9 system with the perfSONAR
repository enabled, and noticed the following unresolved dependency:
java-1.6.0-sun-compat-1.6.0.06-1jpp.i586 from perfsonar-i386 has depsolving
problems
--> Missing Dependency: jdk = 2000:1.6.0_06-fcs is needed by package
java-1.6.0-sun-compat-1.6.0.06-1jpp.i586 (perfsonar-i386)
But when I disable the perfSONAR repository and do a yum localinstall of the
ps-mdm-flowsa-ma and nfdump rpm's after downloading them first, yum decides
to use java-1.5.0-gcj that comes with Fedora 9, and everything works just
fine.
I know that Fedora is one of the unsupported platforms, and on a RHEL 5.2
system everything just seem to work as expected, when I try to install
ps-mdm-flowsa-ma with the perfSONAR repository enabled yum decides to use
the java-1.4.2-gcj-compat that comes with RHEL 5.2.
I am not an dependencies specialist, but is there an easy way to fix the
dependencies so a repository install will work again on Fedora?
Cheers,
HansT.
