Description of problem: Due to an oversight in the rpm spec file qpid-ra-0.10.jar is being picked up from the build/lib directory and installed into the qpid-deps directory as if it was an external jar that the qpid jars depend on. It isn't. How reproducible: Always. Steps to Reproduce: 1. install qpid-java-common-0.10-4.el5.noarch.rpm Actual results: /usr/share/java/qpid-deps/qpid-ra-0.10.jar is installed Expected results: This jar is never expected to be installed
The fix for this is a pretty simple fix to the spec file, which is very low risk. Even though this really isn't in itself a blocking issue it could be confusing. I'd like to get this in if we do respin due to fixing any other problems.
Suggested fix: cvs diff: Diffing . Index: qpid-java.spec =================================================================== RCS file: /cvs/dist/rpms/qpid-java/RHEL-5-MRG/qpid-java.spec,v retrieving revision 1.126 diff -r1.126 qpid-java.spec 3c3 < Release: 4%{?dist} --- > Release: 5%{?dist} 109,110c109,110 < install -p -m 755 $(find build/lib/ -name '*.jar' \ < ! -name 'qpid-client*.jar' ! -name 'qpid-common*.jar') %{buildroot}%{_javadir}/qpid-deps --- > install -p -m 755 build/lib/qpid-deps*.jar %{buildroot}%{_javadir}/qpid-deps > install -p -m 755 build/lib/log4j-slf4j.jar %{buildroot}%{_javadir}/qpid-deps 154a155,157 > * Wed Apr 20 2011 Andrew Stitcher <astitcher> - 0:0.10.-5 > - Removed jar file that was not meant to be in qpid-java-common >
Sounds reasonable to me. Giving it the QA blessing.
This is now checked into the specfile and should happen from 0.10-5 onwards
VERIFIED on rhel5 / rhel6 , i686 / x86_64: qpid-java-common-0.14-1.el6.noarch qpid-java-common-0.14-1.el5
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0529.html