> Subpackage python2-tools is not multilib-clean for x86_64 vs i686: 6 files have > non-equal 32/64bit content: > /usr/bin/smtpd2.7.pyo > /usr/bin/smtpd2.7.pyc > /usr/bin/pygettext2.7.pyo > /usr/bin/pygettext2.7.pyc > /usr/bin/msgfmt2.7.pyo > /usr/bin/msgfmt2.7.pyc Investigation revealed that this is not a new behaviour, it's present in previous versions of Fedora. I believe the proper solution is to remove all these pyc/pyo files in /usr/bin, as Python does not need/use those anyway, since they're not imported but directly launched.
Yes, those files are not supposed to be there.
https://src.fedoraproject.org/rpms/python2/pull-request/41
I've tested that python2-tools is now multilib parallelly installable. $ rpm -qa | grep python2-tools python2-tools-2.7.16-2.fc30.i686 python2-tools-2.7.16-2.fc30.x86_64
python2-2.7.16-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e6d2bef148
python2-2.7.16-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a3fd1d4e7
python2-2.7.16-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a3fd1d4e7
python2-2.7.16-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e6d2bef148
python2-2.7.16-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
python2-2.7.16-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.