Description of problem: - $ rpm -ql pycanberra /pycanberra.py /usr/share/doc/pycanberra /usr/share/doc/pycanberra/COPYING /usr/share/doc/pycanberra/README The second problem is that after the upgrade to Fedora 29 it seems there is no reason for pycanberra to be installed. Nothing uses or requires it. Why is it there? What is it for? I can apparently remove it without causing any problems. Version-Release number of selected component (if applicable): pycanberra-0-0.17.git88c53cd.fc29.noarch al info:
The package is using the %python2_sitelib macro without pulling in some dependency that is required to have it declared. This also means that the portingdb scripts are not detecting the package properly, the python2 subpackage should be dropped in F30.
The only packages still requiring pycanberra are ibus-cangjie and pitivi, which are both Python 3. So dropping the python2 subpackage should be fine. I guess it's too late for Fedora 29 though? As for why it was installed on your system, you might have gotten it as a dependency of something else (e.g Pitivi before it was ported to Python 3), and later uninstalled that. DNF will remove unneeded dependencies when you uninstall the app which had installed them, but if you did that a long time ago with Yum, and then always upgraded your system, that would explain why you still have it.
pycanberra-0-0.18.git88c53cd.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-88ae6ff99e
Yeah, dropping python2 is for F30+. I made a build in rawhide that drops python2.
pycanberra-0-0.18.git88c53cd.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-2018-88ae6ff99e
pycanberra-0-0.18.git88c53cd.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.