Releases retrieved: 3.8.2 Upstream release that is considered latest: 3.8.2 Current version/release in rawhide: 3.8.1-3.fc40 URL: http://www.gnutls.org 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/1221/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gnutls
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-0z2iptw6/gnutls.spec']' returned non-zero exit status 1. StdOut: cat: ./SPECS/gnutls.spec: No such file or directory cat: ./gnutls-3.8.2.tar.xz: No such file or directory cat: ./gnutls-3.8.2.tar.xz.sig: No such file or directory setting SOURCE_DATE_EPOCH=1700006400 error: Bad file: ./gnutls-3.8.2.tar.xz.sig: No such file or directory error: Bad file: ./gnutls-3.8.2.tar.xz: No such file or directory RPM build errors: Bad file: ./gnutls-3.8.2.tar.xz.sig: No such file or directory Bad file: ./gnutls-3.8.2.tar.xz: 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 1999525 [details] Update to 3.8.2 (#2249801)
FEDORA-2023-e075ac32be has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e075ac32be
FEDORA-2023-41b9510adb has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-41b9510adb
FEDORA-2023-41b9510adb 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-41b9510adb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-41b9510adb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-e075ac32be has been pushed to the Fedora 39 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-e075ac32be` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e075ac32be See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-e075ac32be has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-88305f47e2 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-88305f47e2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-88305f47e2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-88305f47e2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.