Releases retrieved: 3.6.1 Upstream release that is considered latest: 3.6.1 Current version/release in rawhide: 3.6.0-1.fc44.1 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
Scratch build failed. Details below: FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/thn-ydz9fz64/https://src.fedoraproject.org/repo/pkgs' Traceback: File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 206, in build output["message"] = self._compare_sources(old_sources, new_sources) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 373, in _compare_sources with open(file_path, "rb") as fd: ^^^^^^^^^^^^^^^^^^^^^ If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
FEDORA-2026-6de223b1e0 (radicale-3.6.1-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6de223b1e0
FEDORA-2026-9679446736 (radicale-3.6.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-9679446736
FEDORA-2026-d8a5fa9d82 (radicale-3.6.1-1.fc44.1) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8a5fa9d82
FEDORA-EPEL-2026-cfc9e528b4 (radicale-3.6.1-1.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-cfc9e528b4
FEDORA-EPEL-2026-339049e29e (radicale-3.6.1-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-339049e29e
FEDORA-EPEL-2026-94ea74c263 (radicale-3.6.1-1.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-94ea74c263
FEDORA-2026-d8a5fa9d82 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d8a5fa9d82` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8a5fa9d82 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-339049e29e 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-2026-339049e29e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-cfc9e528b4 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-2026-cfc9e528b4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-94ea74c263 has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-94ea74c263 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-9679446736 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9679446736` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9679446736 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6de223b1e0 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-2026-6de223b1e0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6de223b1e0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-9679446736 (radicale-3.6.1-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-cfc9e528b4 (radicale-3.6.1-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.
FEDORA-EPEL-2026-94ea74c263 (radicale-3.6.1-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-EPEL-2026-339049e29e (radicale-3.6.1-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-6de223b1e0 (radicale-3.6.1-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-2026-d8a5fa9d82 (radicale-3.6.1-1.fc44.1) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.