Releases retrieved: 2.7.7 Upstream release that is considered latest: 2.7.7 Current version/release in rawhide: 2.7.6-8.fc40 URL: https://keepassxc.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/15656/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/keepassxc
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-9h9bls0c/keepassxc.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1710028800 error: Bad file: ./keepassxc-2.7.7-src.tar.xz.sig: No such file or directory error: Bad file: ./keepassxc-2.7.7-src.tar.xz: No such file or directory RPM build errors: Bad file: ./keepassxc-2.7.7-src.tar.xz.sig: No such file or directory Bad file: ./keepassxc-2.7.7-src.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 2020931 [details] Update to 2.7.7 (#2268750)
Building for test in https://copr.fedorainfracloud.org/coprs/mikelo2/keepassxc-2.7.4/build/7137696/
FEDORA-2024-81c843b00e (keepassxc-2.7.7-2.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-81c843b00e
FEDORA-EPEL-2024-e210a1ba81 (keepassxc-2.7.7-2.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-e210a1ba81
FEDORA-2024-02869f5db8 (keepassxc-2.7.7-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-02869f5db8
FEDORA-EPEL-NEXT-2024-eef086394d (keepassxc-2.7.7-2.el8.next) has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-eef086394d
FEDORA-EPEL-2024-2d4801a0fb (keepassxc-2.7.7-2.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-2d4801a0fb
FEDORA-2024-02869f5db8 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-2024-02869f5db8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-02869f5db8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-e210a1ba81 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-e210a1ba81 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-2d4801a0fb has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-2d4801a0fb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-81c843b00e 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-2024-81c843b00e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-81c843b00e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-8f9c01f90c 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-2024-8f9c01f90c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8f9c01f90c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2024-cd8119ad0f has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-cd8119ad0f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2024-eef086394d has been pushed to the Fedora EPEL 8 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-eef086394d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-1e79adf233 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-2024-1e79adf233` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1e79adf233 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-1e79adf233 (deepin-qt5integration-5.6.11-6.fc40, deepin-qt5platform-plugins-5.6.12-6.fc40, and 49 more) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-01aea3d117 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-01aea3d117 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-65b37f7096 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-2024-65b37f7096` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-65b37f7096 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-cb379daea9 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cb379daea9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2024-a12014c519 has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-a12014c519 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2024-7751cceab0 has been pushed to the Fedora EPEL 8 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-7751cceab0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-65b37f7096 (keepassxc-2.7.8-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.