Bug 1119032
| Summary: | python3-dnf-0.5.3 conflicts with dnf-0.5.2 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
| Component: | dnf | Assignee: | Ales Kozumplik <akozumpl> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | akozumpl, jzeleny, pnemade, rholy, tim.lauridsen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | hawkey-0.4.18-2.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-19 06:03:22 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: | |||
Thanks for the report, reproduced. Fixed by 9615a75. hawkey-0.4.18-2.fc20, dnf-0.5.4-1.fc20, libsolv-0.6.4-0.git2a5c1c4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hawkey-0.4.18-2.fc20,dnf-0.5.4-1.fc20,libsolv-0.6.4-0.git2a5c1c4.fc20 hawkey-0.4.18-2.fc20, dnf-0.5.4-1.fc20, libsolv-0.6.4-0.git2a5c1c4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Error: Transaction check failed*: file /usr/share/man/man8/dnf.8.gz from install of python3-dnf-0.5.3-1.fc20.noarch conflicts with file from package dnf-0.5.2-1.fc20.noarch file /usr/share/man/man8/dnf.conf.8.gz from install of python3-dnf-0.5.3-1.fc20.noarch conflicts with file from package dnf-0.5.2-1.fc20.noarch * or similar, back-translated form Czech Version-Release number of selected component (if applicable): dnf-0.5.3-1.fc20 Steps to Reproduce: 1. Have dnf 0.5.2 installed 2. Install python3-dnf when 0.5.3 is already in the repository 3. Observe the failure Note: Updating dnf first solves the problem. I believe that pythno3-dnf should require dnf = %{version}%{release} to avoid this kind of problems.