Bug 877259
| Summary: | Conflicts with RHEL qemu | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Kevin Fenzi <kevin> |
| Component: | qemu | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el6 | CC: | dwmw2, lkundrak, lubo.rintel, pbonzini, p, redhat-bugzilla, robert.scheck, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-30 15:03:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kevin Fenzi
2012-11-16 04:02:39 UTC
From what we see here, the qemu-img package from EPEL tries to replace the qemu-img package from RHEL - which is inacceptable! --> Processing Dependency: qemu-img = 2:0.12.1.2-2.295.el6_3.2 for package: 2:qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64 ---> Package qemu-img.i686 2:1.2.0-19.el6.1 will be an update I need help with this. Is it somehow possible to blacklist qemu-img.i686 from being propagated into epel/x86_64 repository? Why is that package being built at all? I think that package should be simply
just conditional within the *.spec file by using %{?rhel} and %if(n)arch macro.
Robert, it is in fact conditional and not built in EPEL/x86_64. In RHEL/i686 qemu-img is not available, unlike in RHEL/x86_64. Thus, we only build the i686 version in EPEL. What happens here is that i686 version attempts to update the x86_64 one. (the same applies to qemu-guest-agent I guess) See: https://fedorahosted.org/rel-eng/ticket/4130 https://fedorahosted.org/rel-eng/ticket/4267 Basically we really need some brave soul to hack mash to support whitelist/blacklists and/or work with the way RHEL does multiarch so we don't run into this. ;( Any takers? :) Could you just make this parallel installable? ie, 'qemu12' vs 'qemu' ? It would be a new review, but would avoid at least this issue. Lubomir: Can we please unpush qemu on EPEL 6 testing till this is solved? Lubomir, can you unpush the testing update in bodhi until this is fixed. thanks. Sure, done. Since this package has never been in EPEL (except as part of the testing repo), perhaps we can use a lower Epoch than Fedora and RHEL? Fedora and RHEL use 2, we can use 1. This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |