| Summary: | [PACKAGING] python-qmf-debuginfo should obsolete qpid-cpp-mrg-debuginfo <= 0.9.1073306 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
| Component: | qpid-qmf | Assignee: | Nuno Santos <nsantos> |
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Reznicek <freznice> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | Development | CC: | aortega, esammons, jneedle, matt, mhusnain, tross |
| Target Milestone: | 2.0 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause
Due to package reorganization (namely moving QMF code from the qpid-mrg set of packages to the qpid-qmf set of packages), QMF-related debug symbols moved from qpid-cpp-mrg-debuginfo to python-qmf-debuginfo.
This makes a direct upgrade of debuginfo from 1.3.2 to a later version fail to work due to file conflicts.
Consequence
Installation/upgrade of messaging and qmf packages will fail with file conflicts if debug symbols are installed and requested to automatically update.
Workaround
The workaround is to manually uninstall the previous version of the debuginfo package before attempting to install/upgrade the newer messaging and qmf packages, as such:
$ rpm -ev qpid-cpp-mrg-debuginfo
Result
The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.
Release Note Entry:
File conflicts as a result of package reorganization (the QMF code was moved from the qpid-mrg set of packages to the qpid-gmf set of package) caused direct upgrades of debuginfo from version 1.3.2 to a later version fail if debug symbols were automatically upgraded.
The workaround for this problem is to manually uninstall the previous version of the debuginfo package before an installation or upgrade of the newer messaging and qmf packages is done, such as:
$ rpm -ev qpid-cpp-mrg-debuginfo
This workaround does not introduce any limitations and is simple to execute for users of debuginfo packages.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-23 15:43:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
After consulting with different people, the consensus seems to be that we should release note this (and not support direct update), instead of trying to hack the generation of the debuginfo rpm. The rationale is that people who use debuginfo rpms are knowledgeable enough to handle the extra step of manual removal.
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:
Cause
Due to package reorganization (namely moving QMF code from the qpid-mrg set of packages to the qpid-qmf set of packages), QMF-related debug symbols moved from qpid-cpp-mrg-debuginfo to python-qmf-debuginfo.
This makes a direct upgrade of debuginfo from 1.3.2 to a later version fail to work due to file conflicts.
Consequence
Installation/upgrade of messaging and qmf packages will fail with file conflicts if debug symbols are installed and requested to automatically update.
Workaround
The workaround is to manually uninstall the previous version of the debuginfo package before attempting to install/upgrade the newer messaging and qmf packages, as such:
$ rpm -ev qpid-cpp-mrg-debuginfo
Result
The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.
I'm fine with given technical note. -> VERIFIED
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:
@@ -12,4 +12,14 @@
$ rpm -ev qpid-cpp-mrg-debuginfo
Result
-The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.+The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.
+
+Release Note Entry:
+
+File conflicts as a result of package reorganization (the QMF code was moved from the qpid-mrg set of packages to the qpid-gmf set of package) caused direct upgrades of debuginfo from version 1.3.2 to a later version fail if debug symbols were automatically upgraded.
+
+The workaround for this problem is to manually uninstall the previous version of the debuginfo package before an installation or upgrade of the newer messaging and qmf packages is done, such as:
+
+ $ rpm -ev qpid-cpp-mrg-debuginfo
+
+This workaround does not introduce any limitations and is simple to execute for users of debuginfo packages.
Technical note can be viewed in the release notes for 2.0 at the documentation stage here: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-CONSOLE_Update_Notes-CONSOLE_Update_Notes 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-0890.html |
Description of problem: Recently there was movement of QMF libraries from broker package set (qpid-cpp-mrg) to python-qmf package set. This has the effect of moving debug symbols from qpid-cpp-mrg-debuginfo to python-qmf-debuginfo package. Unfortunately python-qmf-debuginfo does not obsolete older qpid-cpp-mrg-debuginfo packages which contained previous debug symbols of the QMF libs. In other words installation of the messaging + qmf will fail if debug symbols are requested to update: Preparing... ########################################### [100%] file /usr/lib/debug/usr/lib/libqmf.so.3.0.0.debug from install of python-qmf-debuginfo-0.9.1079953-1.el4 conflicts with file from package qpid-cpp-mrg-debuginfo-0.9.1073306-1.el4 file /usr/lib/debug/usr/lib/libqmf2.so.1.0.0.debug from install of python-qmf-debuginfo-0.9.1079953-1.el4 conflicts with file from package qpid-cpp-mrg-debuginfo-0.9.1073306-1.el4 file /usr/lib/debug/usr/lib/libqmfconsole.so.4.0.0.debug from install of python-qmf-debuginfo-0.9.1079953-1.el4 conflicts with file from package qpid-cpp-mrg-debuginfo-0.9.1073306-1.el4 file /usr/lib/debug/usr/lib/libqmfengine.so.3.0.0.debug from install of python-qmf-debuginfo-0.9.1079953-1.el4 conflicts with file from package qpid-cpp-mrg-debuginfo-0.9.1073306-1.el4 Version-Release number of selected component (if applicable): qpid-cpp-*0.9.1079953-1 & python-qmf-*0.9.1079953-1 How reproducible: 100% Steps to Reproduce: 1. install snap1 / 1.3.2 including debuginfos 2. update to snap2 (including debuginfos) Actual results: Upgrade with debuginfo packages from 1.3.2 / 2.0 Snap1 to 2.0 Snap2 not clean (not possible w/o hacks) Expected results: Upgrade with debuginfo packages from 1.3.2 / 2.0 Snap1 to 2.0 Snap2 should be ok. Additional info: