| Summary: | [PACKAGING] qpid-qmf-debuginfo should obsolete python-qmf-debuginfo | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
| Component: | distribution | Assignee: | Nuno Santos <nsantos> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Frantisek Reznicek <freznice> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | Development | CC: | aortega, esammons, iboverma, jross |
| 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 top-level python-qmf package to the qpid-qmf set of packages), some QMF-related debug symbols moved from python-qmf-debuginfo to qpid-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 python-qmf-debuginfo
Result
The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Frantisek Reznicek
2011-03-30 09:23:26 UTC
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 top-level python-qmf package to the qpid-qmf set of packages), some QMF-related debug symbols moved from python-qmf-debuginfo to qpid-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 python-qmf-debuginfo
Result
The workaround does not introduce any limitations, and should prove to be simple to execute for users of debuginfo packages.
Release note explains the problem well. -> VERIFIED |