Releases retrieved: 4.6.0 Upstream release that is considered latest: 4.6.0 Current version/release in rawhide: 4.5.2-1.fc43 URL: http://weechat.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/5122/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/weechat
Created attachment 2081460 [details] Update to 4.6.0 (#2354325)
the-new-hotness/release-monitoring.org's scratch build of weechat-4.6.0-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=130637446
FEDORA-2025-7d1298a4f4 (weechat-4.6.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7d1298a4f4
FEDORA-2025-ed37ed10db (weechat-4.6.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed37ed10db
FEDORA-2025-da6110ec02 (weechat-4.6.0-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-da6110ec02
FEDORA-EPEL-2025-0359e13999 (weechat-4.6.0-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0359e13999
FEDORA-2025-da6110ec02 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-da6110ec02` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-da6110ec02 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ed37ed10db 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-ed37ed10db` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed37ed10db See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-0359e13999 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-2025-0359e13999 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-7d1298a4f4 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-7d1298a4f4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7d1298a4f4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-7d1298a4f4 (weechat-4.6.0-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-EPEL-2025-0359e13999 (weechat-4.6.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-ed37ed10db (weechat-4.6.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-da6110ec02 (weechat-4.6.0-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.