Fedora Account System
Red Hat Associate
Red Hat Customer
Releases retrieved: 2.8, 2.8 Upstream release that is considered latest: 2.8 Current version/release in rawhide: 2.7-12.fc42 URL: http://relax-and-recover.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/36812/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rear
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-mggd647l/rear.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1734566400 error: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory RPM build errors: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.12/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.12/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 2063180 [details] Update to 2.8 (#2333319)
This is currently blocked on the following upstream issue: https://github.com/rear/rear/issues/3375
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-t6mbt0ow/rear.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1738108800 error: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory RPM build errors: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.12/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.12/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 2074282 [details] Update to 2.8 (#2333319)
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-3v7qrnjo/rear.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1738108800 error: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory RPM build errors: Bad file: ./rear-2.8-clean.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.12/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.12/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 2074310 [details] Update to 2.8 (#2333319)
*** This bug has been marked as a duplicate of bug 2343296 ***