Releases retrieved: 2.0.22 Upstream release that is considered latest: 2.0.22 Current version/release in rawhide: 2.0.21-7.fc39 URL: https://uwsgi-docs.readthedocs.org/en/latest/ 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://docs.fedoraproject.org/en-US/package-maintainers/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/6881/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/uwsgi
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-y6zpmnjs/uwsgi.spec']' returned non-zero exit status 1. StdOut: warning: %patchN is deprecated (10 usages found), use %patch N (or %patch -P N) setting SOURCE_DATE_EPOCH=1690502400 error: Bad file: ./uwsgi-2.0.22.tar.gz: No such file or directory RPM build warnings: %patchN is deprecated (10 usages found), use %patch N (or %patch -P N) RPM build errors: Bad file: ./uwsgi-2.0.22.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.11/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.11/site-packages/hotness/builders/koji.py", line 229, in build raise BuilderException( 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
Created attachment 1980404 [details] Update to 2.0.22 (#2227179)
FEDORA-2023-a39d31de27 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a39d31de27
FEDORA-2023-f3e9b8ddd2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f3e9b8ddd2
FEDORA-2023-a39d31de27 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a39d31de27` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a39d31de27 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-f3e9b8ddd2 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f3e9b8ddd2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f3e9b8ddd2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-f3e9b8ddd2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-a39d31de27 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.