Bug 691836

Summary: Add qpid-qmf as new top-level package (no new code, package refactoring)
Product: Red Hat Enterprise Linux 6 Reporter: Nuno Santos <nsantos>
Component: qpid-qmfAssignee: Nuno Santos <nsantos>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: aortega, dgregor, jneedle, jross, syeghiay, tross
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
The qpid-qmf package is now the top-level package for various QMF components which were previously packaged in their own RPM packages (specifically, the python-qmf and qpid-cpp packages).
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:30:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nuno Santos 2011-03-29 15:19:56 UTC
qpid-qmf is a refactored way of packaging the QMF components that were previsouly packaged in different rpms, namely python-qmf and qpid-cpp. 

This means there is no new source code, we're only reusing code that was already present in the source tarballs of those two packages.

Comment 1 RHEL Program Management 2011-03-29 15:38:01 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 2 Nuno Santos 2011-03-29 15:59:20 UTC
To clarify, there is no impact on any shipping product, as this is simply a renaming of content/packages that we were already shipping (and that had already taken place in RHEL 4 and RHEL 5).

Comment 3 Siddharth Nagar 2011-03-30 02:21:07 UTC
OK. The qpid-qmf package will continue to be a part of the system-management-messaging-client comps group which is where python-qmf and qpid-cpp resided. Out of curiosity, what prompted the change?

Comment 4 Dennis Gregorovic 2011-03-30 12:31:39 UTC
Is this a duplicate of bug 679791?

Comment 5 Justin Ross 2011-03-30 14:40:43 UTC
Siddharth, RHEL 6.0 shipped with qmf packaging that diverged and conflicted with that of RHEL 4 and 5.  The new combined qpid-qmf package puts control of those decisions in one place and resolves the conflict.  In short, we had an unmaintainable mess; this new plan is sustainable.

Crucially, it also allows us to rev qmf packages without having to rebuild messaging.

Comment 6 Justin Ross 2011-03-30 15:07:39 UTC
Dennis, I don't think it's a duplicate, though I'm open to a different interpretation.  This issue was created in accordance with the rhel 6 new package process.

Comment 7 Dennis Gregorovic 2011-04-04 20:21:56 UTC
package will be in the next compose

Comment 8 Nuno Santos 2011-04-05 21:39:55 UTC
Dennis: import into PackageWrangler has failed with "Package 'qpid-qmf' is not whitelisted for product 'RHEL-6.1'" (see https://pkgdb.lab.eng.bos.redhat.com/pkg/tasks/wait/9425/ )

Comment 11 Martin Prpič 2011-04-18 13:04:07 UTC
    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:
The qpid-qmf package is now the top-level package for various QMF components which were previously packaged in their own RPM packages (specifically, the python-qmf and qpid-cpp packages).

Comment 12 errata-xmlrpc 2011-05-19 14:30:34 UTC
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-2011-0805.html