$ mock -r fedora-rawhide-x86_64 init $ mock -r fedora-rawhide-x86_64 install fedwatch Problem: package python2-fedmsg-meta-fedora-infrastructure-0.27.0-2.fc30.noarch requires python2.7dist(fedmsg), but none of the providers can be installed - package python2-fedmsg-meta-fedora-infrastructure-0.27.0-2.fc30.noarch requires python2-fedmsg-core, but none of the providers can be installed - package fedwatch-0.5-11.fc30.noarch requires python2-fedmsg-meta-fedora-infrastructure, but none of the providers can be installed - package python2-fedmsg-1.1.1-4.fc30.noarch requires python2-moksha-hub >= 1.3.2, but none of the providers can be installed - conflicting requests - nothing provides python2-stomper needed by python2-moksha-hub-1.5.17-1.fc30.noarch Please switch fedwatch to Python 3 or retire the package. Thanks.
Error: Problem: package fedwatch-0.5-11.fc30.noarch requires fedmsg, but none of the providers can be installed - package fedmsg-1.1.1-4.fc30.noarch requires python2-fedmsg = 1.1.1-4.fc30, but none of the providers can be installed - conflicting requests - nothing provides python2-moksha-hub >= 1.3.2 needed by python2-fedmsg-1.1.1-4.fc30.noarch ---- 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). Thank You!
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
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). Thank You!
See https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro "Packages still failing to install due to a missing Python 2 dependency will be retired at Beta Freeze, assuming they have a Bugzilla bug open for at least 2 weeks. The package maintainer may postpone this retirement to the Final Freeze by promising to fix it until then." Let me know if this package shall not be retired yet. The beta freeze is at 2019-08-29, the final freeze is at 2019-10-08.
Retired the package in master and f31. Let me know if you want me review it once (if) it is added back.
Requesting a freeze exception based on https://pagure.io/fesco/issue/2216#comment-593925
We don't really need a separate FE for every single package that was supposed to be retired but wasn't due to the freeze. We can just file a single bug to cover this situation, I think. I'm unproposing all the separate retirement bugs.
I've verified that the package is gone from the fedora repo. Thanks and sorry for panicking.