Latest upstream release: 3.0.14 Current version/release in rawhide: 3.0.13-2.fc36 URL: http://libical.github.io/libical/ 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://fedoraproject.org/wiki/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/1637/
Created attachment 1859345 [details] Update to 3.0.14 (#2051054)
the-new-hotness/release-monitoring.org's scratch build of libical-3.0.14-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=82443379
FEDORA-2022-38781f4291 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-38781f4291
FEDORA-2022-94bfde125e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-94bfde125e
FEDORA-2022-38781f4291 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-38781f4291` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-38781f4291 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-94bfde125e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-94bfde125e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-94bfde125e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I reported my issue with Fedora 35 and libical 3.0.14 in Bodhi, but it looks like that update was promoted to stable 5 hours prior to my report. I'm not sure my Bodhi report is visible to the maintainers. I suggest that the promotions for other distros (Fedora 34 and CentOS in particular) are held off until the issue is understood. Here's my report from Bodhi https://bodhi.fedoraproject.org/updates/FEDORA-2022-38781f4291 "When creating a new appointment in Evolution, the timezone resets to Atlantic/Reykjavik. If changed manually, it's reset to Atlantic/Reykjavik again when saved. I'm using evolution-3.42.3-1.fc35.x86_64 with corporate calendar in Office 365 through evolution-ews. The whole company is in America/Los_Angeles, and that's my local timezone setting. Restoring libical and libical-glib to version 3.0.13-1.fc35 fixes the problem. The timezone has the correct default and can be edited and saved." I can make a separate issue if it would help.
Created attachment 1860285 [details] Demo of the issue - screen capture
Thanks for the report. After some investigation I see it "broke" the Evolution, which expects on one place (I found only one place, but there can be more) the timezone won't be unset on the re-read of the value from the component. I'd say the libical change uncovered a bug in the Evolution code, rather than the libcal change broke Evolution, because this expectation is not always correct. I'll create an update for Fedora 34, the other Fedoras will be covered with the tomorrow upstream release(s). The change will work fine both with the new and with the old libical. The upstream fix is: https://gitlab.gnome.org/GNOME/evolution/-/commit/9bbb928947
I confirm that the upstream patch fixes Evolution behavior on Fedora 35 with libical-3.0.14-1.fc35.x86_64 when applied to evolution-3.42.3-1.fc35.x86_64 (tested by fedpkg mockbuild with the patch). Thank you!!!
FEDORA-2022-38781f4291 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-94bfde125e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.