similarity index 96%
rename from meta/recipes-support/libical/libical_4.0.6.bb
rename to meta/recipes-support/libical/libical_4.0.7.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=6d9294493d031c817783b0400a126c89 \
SECTION = "libs"
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${BP}.tar.gz"
-SRC_URI[sha256sum] = "2e3729cb69c282d3bb17a8d2b198af6e4bc7502fd3621c9adf573921fe9dceb0"
+SRC_URI[sha256sum] = "47c05bc96e41416578cf1803bb2ba3f8d292cb17d5ac2fca539dee922bae8a94"
inherit cmake pkgconfig gobject-introspection vala github-releases
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libical* to *4.0.7* has Succeeded. Next steps: - apply the patch: git am 0001-libical-upgrade-4.0.6-4.0.7.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 8239133c9ebee31ccee9238bb0a797834d8ab3cb Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 19 Oct 2026 05:51:53 +0000 Subject: [PATCH] libical: upgrade 4.0.6 -> 4.0.7 # Libical v4.0.6 ## Overview This is a patch release and is fully source and binary compatible with version 4.0.0. [Note: the libicalvcard is a released as a *Technical Preview*. As such, its API is not finalized and no source or binary compatibility is guaranteed with that library in the 4.0.x series.] ## ReleaseNotes - libicalvcard: - `vcardcomponent_clone()` and friends now deep-copy TEXTLIST values (e.g. NICKNAME, CATEGORIES) and structured parameters (JSCOMPS), and keep the property group. Previously the clone shared them with the original, so freeing both freed the same memory twice. - Fixed a use-after-free and a memory leak when converting a vCalendar procedure alarm (PALARM) whose attachment is a plain path name. - libical: - Fix busy status of recurring events in `icalcomponent_foreach_recurrence()`. - Fix `icalvalue_decode_ical_string()` and `icallangbind_property_eval_string()` reading past the end of a string that ends in a backslash or a newline. - `icaltimezone_truncate_vtimezone()` no longer reads the RRULE after freeing it when the new DTSTART is within a year of UNTIL (RSCALE rules), and no longer uses an uninitialized onset when no RRULE occurrence falls before the window close. - Fix IMAGE and STRUCTURED-DATA given by URI (with or without VALUE=URI) parsing to a URI value, whose string `icalproperty_get_image()` and `icalproperty_get_structureddata()` then read as an icalattach pointer. - Fix use-after-free and double free in `icalcomponent_merge_component()` when both calendars have a VTIMEZONE with the same TZID. Every VTIMEZONE of the merged calendar is now merged, and a conflicting VTIMEZONE is added under a renamed TZID (e.g. "Zone1") that its events use. - Fix out-of-bounds access to the year days bitmask in the recurrence iterator when an RSCALE date falls outside the year (e.g. BYWEEKNO with a DTSTART before the calendar's epoch). - Fix `icalrecur_iterator_set_range()` for a reverse range on a rule without UNTIL, which started the iteration at year 0 instead of at 'from'. - Fix `icalparser_clean()` for proper reuse by resetting internal structure values and clearing the root component to avoid a use-after-free. - Behavior change: The typed icalvalue getters now check that the value type of the icalvalue uses the same union member as the expected value type of the getter, as the vcardvalue getters have done since version 4.0.6. If the type mismatches, then they return the zero value for the expected value type. The typed setters error with ICAL_BADARG_ERROR instead of overwriting a value held in another union member. - libicalss: - Fix heap-buffer-overflow in `icalspanlist_as_freebusy_matrix()` for busy spans that start before or end after the spanlist. `icalspanlist_from_vfreebusy()` now sets the spanlist start/end from DTSTART/DTEND and marks FBTYPE=FREE periods as free (all others as busy). - Buildsystem changes: - Fix CMake command target_link_libraries() to use all-keywords as required since CMake v4.4.4. - When cross-compiling, don't build/install ical-glib-src-generator w/o existing binary Please see the [CHANGELOG](https://github.com/libical/libical/blob/4.0/CHANGELOG.md) for more. --- .../libical/{libical_4.0.6.bb => libical_4.0.7.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/libical/{libical_4.0.6.bb => libical_4.0.7.bb} (96%)