Bug 593636 - Rebase build on upstream apache qpid r.946106
Rebase build on upstream apache qpid r.946106
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Kim van der Riet
MRG Quality Engineering
: Rebase
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-19 07:28 EDT by Kim van der Riet
Modified: 2010-11-10 16:27 EST (History)
3 users (show)

See Also:
Fixed In Version: qpid-cpp-0.7.946106-1
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-10 16:27:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Kim van der Riet 2010-05-19 07:28:26 EDT
In order to synchronize the RHEL-6 build as closely as possible to the RHEL-4/5 builds for MRG v1.3 beta 2, and in order to share the same source tarballs, the next build of qpid-cpp will be rebased to qpid svn r.946106. This fixes numerous bugs that would otherwise have to be inevitably patched in order to produce an acceptable release.

The plan is to patch all future builds of MRG 1.3 on this base.
Comment 3 RHEL Product and Program Management 2010-05-19 13:28:21 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 7 releng-rhel@redhat.com 2010-11-10 16:27:42 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.