Releases retrieved: 0.33.0 Upstream release that is considered latest: 0.33.0 Current version/release in rawhide: 0.32.0-1.fc40 URL: https://github.com/release-engineering/kobo 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/12359/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/kobo
Created attachment 1995317 [details] Update to 0.33.0 (#2245972)
the-new-hotness/release-monitoring.org's scratch build of kobo-0.33.0-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=108050079
FEDORA-2023-26297483b8 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-26297483b8
FEDORA-EPEL-2023-c7e7e956a3 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c7e7e956a3
FEDORA-2023-e5268d03f2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e5268d03f2
FEDORA-2023-dacbd8ec5b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dacbd8ec5b
FEDORA-EPEL-2023-55ed36d7ba has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-55ed36d7ba
FEDORA-2023-26297483b8 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-e5268d03f2 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-e5268d03f2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e5268d03f2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-55ed36d7ba 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-2023-55ed36d7ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-c7e7e956a3 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-2023-c7e7e956a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-dacbd8ec5b 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-dacbd8ec5b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dacbd8ec5b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-55ed36d7ba 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-2023-c7e7e956a3 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-dacbd8ec5b has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-e5268d03f2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.