Releases retrieved: 2.2 Upstream release that is considered latest: 2.2 Current version/release in rawhide: 2.1-4.fc39 URL: https://github.com/jarun/ddgr/ 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/16976/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/ddgr
Created attachment 2006658 [details] Update to 2.2 (#2256282)
the-new-hotness/release-monitoring.org's scratch build of ddgr-2.2-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=111071614
Any chance of this being released? This "new" version has been published on GH for nearly a year now
FEDORA-2025-15c630b0e8 (ddgr-2.2-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-15c630b0e8
FEDORA-2025-34173b928e (ddgr-2.2-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-34173b928e
FEDORA-EPEL-2025-361f7a5430 (ddgr-2.2-1.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-361f7a5430
FEDORA-EPEL-2025-523ed9e38d (ddgr-2.2-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-523ed9e38d
FEDORA-2025-15c630b0e8 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-15c630b0e8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-15c630b0e8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-523ed9e38d 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-523ed9e38d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-361f7a5430 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-361f7a5430 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-34173b928e 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-34173b928e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-34173b928e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-523ed9e38d (ddgr-2.2-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-EPEL-2025-361f7a5430 (ddgr-2.2-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-15c630b0e8 (ddgr-2.2-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-34173b928e (ddgr-2.2-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.