+++ This bug was initially created as a clone of Bug #1646883 +++ Description of problem: Issue "dnf update" on my Fedora 28 installation. Results in "Transaction check error". Version-Release number of selected component (if applicable): Fedora 28 How reproducible: Issue "dnf update" Steps to Reproduce: 1. 2. 3. Actual results: transaction check error Expected results: updates system. Additional info: see attached file (output of dnf update ) --- Additional comment from Jaroslav Mracek on 2018-11-27 06:53:56 EST --- The issue is created by file conflict as a result of packaging issue. I ceated an issue (https://pagure.io/packaging-committee/issue/834) to ask packaging committee for recommended solution and to enhance packaging guidelines. From your report I can see that the issue is related to list of following packages: p11-kit gnutls elfutils-libelf glib2 pcre2 Please can you --- Additional comment from Jaroslav Mracek on 2018-11-27 06:59:15 EST --- Because the issue in packaging of other packages - changing component. Please can you solve the issue in your package? You can use following solution or wait for packaging committee for recommendation: Conflict can help: Conflicts: <pkg_name> < %{version}-%{release} Or movement of shared files into noarch package could also help.
From the DNF log: file /usr/share/doc/pcre2/ChangeLog from install of pcre2-10.32-3.fc28.i686 conflicts with file from package pcre2-10.31-11.fc28.x86_64 file /usr/share/doc/pcre2/NEWS from install of pcre2-10.32-3.fc28.i686 conflicts with file from package pcre2-10.31-11.fc28.x86_64 file /usr/share/licenses/pcre2/LICENCE from install of pcre2-10.32-3.fc28.i686 conflicts with file from package pcre2-10.31-11.fc28.x86_64
Please note that this is not really bug in the pcre2 packaging but deficiency of DNF that it does not properly keep multilib packages in sync.
Yeah, it's not pcre's fault either. Yum had a special tracking for this, it'd error out with "protected multilib versions" in such a situation. If dnf doesn't have that then perhaps it should be reconsidered.
*** Bug 1646883 has been marked as a duplicate of this bug. ***
I don't feel comfortable with "fixing" only this one package if I maintain hundreds of affected packages. I will wait for the FPC resolution.
don't you need "dnf update --best" to work correctly with multilib?
*** Bug 1653676 has been marked as a duplicate of this bug. ***
*** Bug 1653682 has been marked as a duplicate of this bug. ***
*** Bug 1576944 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's 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 Fedora 'version' of '28'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1717218 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's 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 Fedora 'version' of '31'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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 Fedora 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.