Description of problem: JBoss ON needs a postgres version > 8.2.4 . The RHEL supplied 8.1 is not usable. Customers on RHEL that want to use JBoss ON need to download Postgres from 3rd party. As Postgres is as of now at 8.3.6 and 8.3 has many superior features over 8.2.x , I am asking for 8.3.6+ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We will not change base RHEL-5 to use anything but Postgres 8.1, because of the incompatibilities (particularly in on-disk data format) between that release series and later ones. Sorry, but an update just wouldn't fly. We do ship later Postgres release series as part of our Application Stack product. That's on 8.2.x at the moment, but it's possible that there might be an AppStack V3 release series with 8.3.x (or more likely 8.4.x by the time it happens). As far as JBoss goes, what's the problem with requiring AppStack to be installed? I thought it already depended on other parts of that anyway.
The problem is that the customer needs to have a app stack entitlement, which they only need for this version of postgres. Note: we are not talking of Jboss in general, but about JBoss Operations Network And: I have opened this entry after Subhendu Ghosh told me to do exactly this. I did not ask to replace existing postgres 8.1, but to *additionally* deliver 8.3.6+ too
Setting dev ack on Tom's behalf, this will bring an upstream point release in to RHEL5.5.
Package review request created.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: On IA64, the installed development subpackage architecture must match the intended target architecture. While it is possible to install both i386 and ia64 packages, these contain conflicting files and using the both architectures together may lead to unpredictable results.
(In reply to comment #29) Per today's discussion on os-devel-list, it would probably be better to say that in general, installation of i386 -devel packages on ia64 is not supported; and in fact is pointless because the ia64 compiler is not capable of building i386 binaries. postgresql84 is far from unique in having conflicts here (I'm certain that postgresql and mysql do too, and that's just in my own packages).
(In reply to comment #30) Yes, right, unfortunately I got the link only after writing that. I've tried to improve the note ... well, maybe it'd be better for ECS to start from scratch, I don't like my text.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -On IA64, the installed development subpackage architecture must match the intended target architecture. While it is possible to install both i386 and ia64 packages, these contain conflicting files and using the both architectures together may lead to unpredictable results.+On IA64, the only supported development subpackage architecture is ia64. While it is possible to install both i386 and ia64 packages, these contain conflicting files and using the both architectures together may lead to unpredictable results. The i386 version is unsupported, as the ia64 version of gcc cannot compile code executable using the IA32 emulation capability.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~ RHEL 5.5 Beta has been released! There should be a fix present in this release that addresses your request. Please test and report back results here, by March 3rd 2010 (2010-03-03) or sooner. Upon successful verification of this request, post your results and update the Verified field in Bugzilla with the appropriate value. If you encounter any issues while testing, please describe them and set this bug into NEED_INFO. If you encounter new defects or have additional patch(es) to request for inclusion, please clone this bug per each request and escalate through your support representative.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2010-0276.html