Releases retrieved: 2.1.7-rc2 Upstream release that is considered latest: 2.1.7-rc2 Current version/release in rawhide: 2.1.7-0.2.rc1.fc40 URL: https://clusterlabs.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/2584/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/pacemaker
Created attachment 2001338 [details] Update to 2.1.7-rc2 (#2251425)
the-new-hotness/release-monitoring.org's scratch build of pacemaker-2.1.7-rc2.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=109511671
FEDORA-2023-5a0dd9dc5d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a0dd9dc5d
FEDORA-2023-074a5c400d has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-074a5c400d
FEDORA-2023-074a5c400d 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-074a5c400d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-074a5c400d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5a0dd9dc5d 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-5a0dd9dc5d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a0dd9dc5d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-fe9f6ae812 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-fe9f6ae812
FEDORA-2023-fe9f6ae812 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-fe9f6ae812` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fe9f6ae812 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-074a5c400d has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-587433efea 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-587433efea` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-587433efea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-2ff43e0fc2 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-2ff43e0fc2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-2ff43e0fc2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-2ff43e0fc2 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.