Latest upstream release: 34.0
Current version/release in rawhide: 33.0-1.fc37
Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.
Based on the information from Anitya: https://release-monitoring.org/project/18441/
Scratch build failed. Details bellow:
GenericError: File upload failed: cli-build/1647265252.395965.QzoQIIBB/python-readme-renderer-34.0-1.fc34.src.rpm
File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
result = self.builder.build(request.package, request.opts)
File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 198, in build
output["build_id"] = self._scratch_build(session, package.name, srpm)
File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 451, in _scratch_build
File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 3027, in uploadWrapper
self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume)
File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 2962, in fastUpload
raise GenericError("File upload failed: %s/%s" % (path, name))
If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
FEDORA-2022-fb95eff89f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fb95eff89f
FEDORA-2022-fb95eff89f has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.