libstdc++ package conflicts between i686 and x86_64 Appears to be the same bug as in https://bugzilla.redhat.com/show_bug.cgi?id=1366516 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 Reproducible: Always Steps to Reproduce: 1. sudo dnf upgrade -y 2. download and wait for package install 3. get error Actual Results: - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64 Expected Results: upgrade completes correctly without errors Appears to be the same bug as in https://bugzilla.redhat.com/show_bug.cgi?id=1366516
Indeed. Doesn't happen with gcc-14.1.1-5.fc41 because the shared files have the same contents there. The only change since then is a clean rebase+bump. An upstream issue is a possibility but, and more likely, something funny happened during the build...
Or a python3 bug?
See Bug 2293940 which has been re-assigned to the add-determinism component. Can this bug be closed as a dup of that one?
> Can this bug be closed as a dup of that one? I'm not sure. Yes, apparently we need bz2294381 to be fixed first but that wouldn't make the libstdc++ conflict disappear. But then we still need to rebuild gcc to resolve it...
OK, let's use the other one for the underlying bug and this one for the required gcc rebuild.
This is a bug in the gcc specfile, so there is no need for 2 separate bugzillas. I am marking this one as a duplicate. It was opened earlier, but the other one includes my findings and possible fix. *** This bug has been marked as a duplicate of bug 2294381 ***