Hi Hans,
Hans Trompert wrote:
Hi Mario,
The nfdump package does not depend on java:
$ yum deplist nfdump | grep -v provider
Loaded plugins: fastestmirror, refresh-packagekit
Finding dependencies:
package: nfdump.i386 1.5.7-1
dependency: libc.so.6(GLIBC_2.3)
dependency: libc.so.6(GLIBC_2.1)
dependency: libc.so.6
dependency: libresolv.so.2
dependency: libc.so.6(GLIBC_2.0)
dependency: rtld(GNU_HASH)
dependency: /bin/sh
dependency: libc.so.6(GLIBC_2.2)
But tomcat5 does. And looking at the dependencies for tomcat5:
[dependencies deleted]
dependency: java-devel >= 1.4.2
provider: java-1.6.0-openjdk-devel.i386 1:1.6.0.0-0.18.b09.fc9
provider: java-1.5.0-sun-compat.i586 1.5.0.14-1jpp
provider: java-1.6.0-sun-compat.i586 1.6.0.06-1jpp
provider: java-1.5.0-gcj-devel.i386 1.5.0.0-21.fc9
provider: java-1.6.0-openjdk-devel.i386 1:1.6.0.0-0.10.b09.fc9
[even more dependencies deleted]
You can see that even though java-1.5.0-gcj.i386 is already installed on
the system, yum does not decide to install java-1.5.0-gcj-devel.i386 to
solve the dependency but decides to install the package with the highest
version number -> java-1.6.0-sun-compat.i586 1.6.0.06-1jpp (the one from
the perfSONAR repository).
I don't get this. Why do we need Java on a pS repository at all ?
On the pS 3.1 admin guide we said that JAVA has to be installed
independently from pS - previous to the pS installation.
What for do we need these 2 java RPMs in
http://downloads.perfsonar.eu/repositories/rpm/testing/i386/Packages/
? They seems to be there since Nov the 10th.
I think best way to have a consistent Java environment for Linux is
to use Jpackage irrespective of the possible already installed
versions on the OS.
Personally, I would try to avoid OS built-in java versions as much as
possible.
Otherwise one is bound to get this sort of misalignment between Tomcat
and the required underlying Java.
I have no idea if and how you can force yum to install the -devel package
that corresponds with the already installed java-1.5.0-gcj.i386.
Neither do I. That's why I think it's even easier to stick to the
Java-related package set provided by Jpackage, as much as possible.
It's probably even easier than configuring yum to act as we'd love to
act, assuming it actually is possible with some sort of client config.
ciao
Mario
Cheers,
HansT.
On Thu, 13 Nov 2008, Mario Reale wrote:
Hi Hans
it states:
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
I might be wrong, but it seems to me that for some reason java
-1.6-sun-compat first appears while handling nfdump itself through Java
Mario
Hans Trompert wrote:
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.
|
