Releases retrieved: 2.7 Upstream release that is considered latest: 2.7 Current version/release in rawhide: 2.6-14.fc42 URL: http://heasarc.gsfc.nasa.gov/fitsio/CCfits/ 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/258/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/CCfits
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-3actj7wv/CCfits.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1741910400 error: Bad file: ./CCfits-2.7.tar.gz: No such file or directory RPM build errors: Bad file: ./CCfits-2.7.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 2080288 [details] Update to 2.7 (#2352641)
FEDORA-2025-a6ade64c48 (CCfits-2.7-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-a6ade64c48
FEDORA-2025-a8a5e3c657 (CCfits-2.7-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-a8a5e3c657
FEDORA-2025-a8a5e3c657 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a8a5e3c657` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a8a5e3c657 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-a6ade64c48 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a6ade64c48` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a6ade64c48 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-98d7c10573 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-98d7c10573` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-98d7c10573 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-a6ade64c48 (CCfits-2.7-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-98d7c10573 (CCfits-2.7-1.fc40.1) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-a8a5e3c657 (CCfits-2.7-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.