Red Hat Bugzilla – Bug 1113159
Failing to install rhevm-sdk-java with JBoss 6.3.0
Last modified: 2016-03-09 14:55:29 EST
Description of problem: Package 'rhevm-sdk-java' requires the following packages: httpcomponents-httpclient httpcomponents-httpcore However in JBoss 6.3.0 they where renamed to: httpcomponents-client httpcomponents-core Version-Release number of selected component (if applicable): How reproducible: Using the following repositories : [1] http://download.devel.redhat.com/devel/candidates/JBEAP/composing/JBEAP-6.3.0-RHEL-6-20140612.0/compose/Server/x86_64/os/ [2] http://bob.eng.lab.tlv.redhat.com/builds/av9.4/el6 Steps to Reproduce: 1. yum install rhevm-sdk-java Actual results: Error: Package: rhevm-sdk-java-3.4.1.0-2.el6ev.noarch (rhevm) Requires: httpcomponents-httpclient >= 4.2.1 Error: Package: rhevm-sdk-java-3.4.1.0-2.el6ev.noarch (rhevm) Requires: httpcomponents-httpcore >= 4.2.1 Expected results: Complete! Additional info: In JBoss 6.1.0 the packages where provided by 'httpclient' and 'httpcore'.
Users will use RHN, where the old packages will still be available, so this isn't a problem for them. However, the EAP team has recommended to update the dependencies, as the old packages won't get fixes. We will do this once EAP 6.3 is released.
Created attachment 916194 [details] Proposed patch
I believe that the proposed patch will fix this issue. However I'm not 100% sure which will be the names of the packages, as I see many related packages in the temporary repositories that we use for testing, some of them empty. I will delay merging/building the fix till EAP 6.3.0 is released and I can check which are actually the packages available in RHN.
JBoss EAP 6.3 has been released and is now available in RHN. I verified that the new httpclient-eap6 and httpcore-eap6 packages are available. So are the old httpcomponents-httpclient and httpcomponents-httpcore packages, which confirms that the change isn't needed. Location of the .jar files provided by the packages are different, as expected. If we do the change this won't cause a problem to build or install the rhevm-sdk-java package, but it will cause problems for users that have scripts that use the path names. For example, if a user has a script containing something like this: java -classpath -classpath \ myapp.jar:\ /usr/share/java/rhevm-sdk-java/rhevm-sdk-java.jar:\ /usr/share/java/httpclient.jar \ $CLASSPATH my.app.Main It will fail, as the location of the httpclient.jar provided by the new httpclient-eap6 package is /usr/share/java/httpcomponents-eap6/httpclient.jar (note that directory is different). All in all, if we change we can break existing user scripts, if we don't change we don't benefit from the updates (the old EAP packages won't be udpated). What do we want to do?
I would go with the change and add release note.
Verified using the following repositories: Using the following repositories : [1] http://download.devel.redhat.com/devel/candidates/JBEAP/composing/latest-JBEAP-6.4-RHEL-6/compose/Server/x86_64/os/ [2] http://bob.eng.lab.tlv.redhat.com/builds/av9.4/el6 Successfully installed: rhevm-sdk-java-3.4.1.0-2.el6ev.noarch httpcomponents-project-6-7.redhat_1.ep6.el6.noarch httpcomponents-core-4.2.1-7.redhat_1.ep6.el6.noarch httpcomponents-client-4.2.1-7.redhat_1.ep6.el6.noarch
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. https://rhn.redhat.com/errata/RHEA-2016-0405.html