Unable to install a specific version of JBoss EAP via yum

Issue

• How to install JBoss EAP 5.1.1 using the RPM software channel and not the very last version available?

Having checked that I am subscribed to the right channel using the # rhn-channel -l

    jbappplatform-5-x86_64-server-6-rpm
    rhel-x86_64-server-6
    rhel-x86_64-server-fastrack-6
    rhel-x86_64-server-supplementary-6
    rhn-tools-rhel-x86_64-server-6

I am trying to install jbossass version 5.1.1, but it will notinstall. This is what seems to be the error message:

   Package jbossas-messaging511 is obsoleted by jbossas-messaging, but obsoleting package does not provide for requirements

Here is the output from my terminal window:

# yum install jbossas-5.1.1-17.ep5.el6 --skip-broken
Loaded plugins: product-id, rhnplugin, subscription-manager
Updating certificate-based repositories.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package jbossas.noarch 0:5.1.1-17.ep5.el6 will be installed
--> Processing Dependency: jbossas-client = 5.1.1-17.ep5.el6 for
package: jbossas-5.1.1-17.ep5.el6.noarch
--> Processing Dependency: jbossas-jms-provider = 5.1.1-1 for package:
jbossas-5.1.1-17.ep5.el6.noarch
Package jbossas-messaging511 is obsoleted by jbossas-messaging, but
obsoleting package does not provide for requirements
--> Processing Dependency: jbossas-ws-stack = 5.1.1-1 for package:
jbossas-5.1.1-17.ep5.el6.noarch
--> Processing Dependency: jboss-common-logging-log4j >= 2.1.2 for
package: jbossas-5.1.1-17.ep5.el6.noarch
--> Processing Dependency: jboss-security-xacml >= 2.0.5 for package:
[..]

• How can we install an RPM for a non-current JBoss version?

• How to upgrade to 6.3.3 with yum-update?

  • We have EAP 6.3.1.GA in production. We wanted to upgrade to 6.3.3. We have yum update to use with Spacewalk, but it has the opportunity to provide us the last 6.4.0 version. Is it possible to get the 6.3.3 version with yum-update through Spacewalk?
  • Our jboss setup does not want to care the CLI command: patch apply. Why? Could it be that the CLI-components was not delievered by Spacewalk because of using yum-update?