Fedora Account System
Red Hat Associate
Red Hat Customer
Releases retrieved: 3.7.5 Upstream release that is considered latest: 3.7.5 Current version/release in rawhide: 3.7.4-1.fc45.2 URL: https://radicale.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/5730/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/radicale
Created attachment 2145330 [details] Update to 3.7.5 (#2488733)
the-new-hotness/release-monitoring.org's scratch build of radicale-3.7.5-1.fc44.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=146611423
Releases retrieved: 3.7.8 Upstream release that is considered latest: 3.7.8 Current version/release in rawhide: 3.7.7-1.fc45 URL: https://radicale.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/5730/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/radicale
Created attachment 2153790 [details] Update to 3.7.8 (#2488733)
the-new-hotness/release-monitoring.org's scratch build of radicale-3.7.8-1.fc44.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=148767264
FEDORA-EPEL-2026-9b446476bf (radicale-3.7.8-1.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-9b446476bf
FEDORA-2026-f090c4c593 (radicale-3.7.8-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f090c4c593
FEDORA-EPEL-2026-4241dcb24d (radicale-3.7.8-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-4241dcb24d
FEDORA-EPEL-2026-c4c94cf2cc (radicale-3.7.8-1.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c4c94cf2cc
FEDORA-2026-1a1afac518 (radicale-3.7.8-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-1a1afac518
FEDORA-EPEL-2026-c4c94cf2cc (radicale-3.7.8-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-1a1afac518 (radicale-3.7.8-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-4241dcb24d (radicale-3.7.8-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-2026-f090c4c593 (radicale-3.7.8-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-9b446476bf (radicale-3.7.8-1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.