Releases retrieved: 0.80 Upstream release that is considered latest: 0.80 Current version/release in rawhide: 0.79-1.fc40 URL: http://www.chiark.greenend.org.uk/~sgtatham/putty/ 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/5749/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/putty
Created attachment 2004850 [details] Update to 0.80 (#2255025)
the-new-hotness/release-monitoring.org's scratch build of putty-0.80-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=110509470
FEDORA-2024-fed5307ae3 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-fed5307ae3
FEDORA-2024-fed5307ae3 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-d946b9ad25 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-d946b9ad25
FEDORA-2024-71c2c6526c has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-71c2c6526c
FEDORA-EPEL-2024-f0d88b447f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f0d88b447f
FEDORA-EPEL-2024-155a6ac298 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-155a6ac298
FEDORA-2024-d946b9ad25 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-d946b9ad25` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-d946b9ad25 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-71c2c6526c 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-71c2c6526c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-71c2c6526c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-f0d88b447f 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-f0d88b447f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-155a6ac298 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-155a6ac298 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-f0d88b447f has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-155a6ac298 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-d946b9ad25 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-71c2c6526c has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.