 |
 |
Hi Jean-Michel, Jean-Michel Barbet wrote: > Antun Balaz wrote: > >> using the procedure outlined in the guide I sent you, you can uninstall >> jdk-1.5.0_14-fcs and java-1.5.0-sun-compat-1.5.0.14-1jpp and avoid all >> problems. The guide is available at: > > Thanks Antun, > > Here is what I did : > > # wget > http://glite.phy.bg.ac.yu/GLITE-3/java/java-1.5.0-sun-1.5.0.14-1jpp.i586.rpm > > # rpm -e --nodeps jdk java-1.5.0-sun-compat-1.5.0.14-1jpp > # rpm -ivh java-1.5.0-sun-1.5.0.14-1jpp.i586.rpm > # yum upgrade > [...] > Dependencies Resolved > > Seems to cure the problem. > > Still I have difficulties to understand the origin of this issue. > I have found the following post : > https://zarb.org/pipermail/jpackage-discuss/2008-January/012256.html > > I understand that the jdk package distributed with sl-errata has > an unversioned dependency on xml-commons-apis : > rpm -q --provides jdk > jre = 1.5.0_14 > j2sdk = 1.5.0_14 > j2re = 1.5.0_14 > jaxp_parser_impl > xml-commons-apis > > And there is one updated package that require also xml-commons-apis > maybe at a different version which would trrigger the removal of > jdk while it is not possible.... ? > > Actually log4J requires xml-commons-apis : > rpm -q --whatrequires xml-commons-apis > log4j-1.2.14-3jpp > > But I cannot find which package is providing it now that I > replaced jdk and java-1.5.0-sun-compat-1.5.0.14-1jpp by the > new java-1.5.0-sun-1.5.0.14-1jpp from glite.phy.bg.ac.yu... > > Anyone can finish the story ? > welcome to RPM dependency hell... we've ran into similar issues before (try installing and upgrading j2sdk 1.4 and jdk 1.5 on the same box) . Here's what happens when trying to install tomcat 5.5 from jpackage: - tomcat 5.5 requires xml-commons-apis >= 1.3 - jpackage provides a package xml-commons-apis-1.3 - jdk provides xml-commons-apis with no version number - yum/rpm decides that it wants to "upgrade" the package xml-commons-apis : this means installing the new version of the xml-commons-apis package and REMOVING all other packages that provide xml-commons-apis (this is a design feature of RPM, not a bug, so I have been told by the RPM mailing list) - rpm thus wants to REMOVE the jdk package as it provides "obsolete" functionality - removing the jdk will break dependencies on other packages, hence the complete installation fails... the only real solution is to get rid of these crazy cross-dependencies in the jdk package , as is done by rolling your own RPM. Similar problems occur when installing/using jpackage 'ant' , BTW. cheers, JJK / Jan Just Keijser Nikhef Amsterdam