$ mock -r fedora-rawhide-x86_64 install pysysbot ... Error: Problem: conflicting requests - nothing provides python2.7dist(jabberbot) needed by pysysbot-0.1.3-10.fc30.noarch Please fix this or retire the package.
A week has passed and this bug is still in the NEW state and the package does not install. Please fix this or indicate that you are working ona fix by setting the state to ASSIGNED. After 3 such reminders, this package may be orphaned. https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro Thanks
In preparation for the Python 2 EOL, we are removing all non-installable Python 2 packages: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned. Note that you don't have to actually fix this right now, setting the bug to ASSIGNED will just mark this as being worked on, so I'll know it is being taken care of. If this happens too quickly, feel free to reach to me any time for help (with specific problems). (My previous comment might have come across a bit too aggressive. I'm sorry, that was not my intention.) (If you know for sure this package shall be removed, consider doing it.) Thank You!
pysysbot-0.3.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-30bc2cf394
Thanks!
pysysbot-0.3.0-1.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-30bc2cf394
pysysbot-0.3.0-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.