Releases retrieved: 0.190 Upstream release that is considered latest: 0.190 Current version/release in rawhide: 0.189-6.fc40 URL: https://sourceware.org/elfutils/ 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/5679/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/elfutils
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-vkybkm7a/elfutils.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1698969600 error: Bad file: ./elfutils-0.190.tar.bz2: No such file or directory RPM build errors: Bad file: ./elfutils-0.190.tar.bz2: 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 1997016 [details] Update to 0.190 (#2247830)
FEDORA-2023-70de8a8207 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-70de8a8207
FEDORA-2023-70de8a8207 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-70de8a8207` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-70de8a8207 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-70de8a8207 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-0568d68196 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0568d68196
FEDORA-2023-0862a2ca46 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0862a2ca46
FEDORA-2023-0568d68196 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-0568d68196` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0568d68196 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-0862a2ca46 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-0862a2ca46` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0862a2ca46 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-0568d68196 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-0862a2ca46 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.