From patchwork Fri Sep 18 05:47:12 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 98661 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 414BEC982D9 for ; Fri, 18 Sep 2026 05:47:16 +0000 (UTC) Received: from a27-33.smtp-out.us-west-2.amazonses.com (a27-33.smtp-out.us-west-2.amazonses.com [54.240.27.33]) by mx.groups.io with SMTP id smtpd.msgproc01-g2.4956.1789710433625615250 for ; Thu, 17 Sep 2026 22:47:13 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=nnubsmUx; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=b5hRxuiN; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.33, mailfrom: 010101a0b30df7f4-fe18f641-bf1c-441b-917d-4c676fead2ea-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1789710432; h=Content-Type:MIME-Version:From:To:Subject:Message-Id:Date; bh=XwHxrEsANNpqrgga0BAkosYlLIR1+6kEgujs3j7xK74=; b=nnubsmUx6uNqEnVJMR91pWnqSjgV1lzspwIDMKq+Xad32hd6WfKx1GUejEoDVYYf UYaZiz6oSS4MeLts5lw+6O0V+r9J/lBQk96WyVqzzKfzFhTgap8YnRWSHn5HeGw5QLJ H/L3M3G4UvEi6BjBM1S9QPFir6ifT4E/2TaZN81Y= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1789710432; h=Content-Type:MIME-Version:From:To:Subject:Message-Id:Date:Feedback-ID; bh=XwHxrEsANNpqrgga0BAkosYlLIR1+6kEgujs3j7xK74=; b=b5hRxuiNCpNggJlBeDEnRNAIwYILy7PC2BWiMjMLTyWkF20wDWVwLs2wyuZSduar m7JBWpqReCMSfTdbj/tNgycqcocdjOvDR+FFWwwgjoEN55hiVa/GEeqka35OYvnDMNb Gj+J1Jqc7xsutC8Ag1fbC9wE55ePXAsSN+Vk5Rys= MIME-Version: 1.0 From: auh@yoctoproject.org To: openembedded-core@lists.openembedded.org Subject: [AUH] tzcode-native,tzdata: upgrading to 2026d,2026d FAILED Message-ID: <010101a0b30df7f4-fe18f641-bf1c-441b-917d-4c676fead2ea-000000@us-west-2.amazonses.com> Date: Fri, 18 Sep 2026 05:47:12 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.09.18-54.240.27.33 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Fri, 18 Sep 2026 05:47:16 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/246181 Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *tzcode-native,tzdata* to *2026d,2026d* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-tzcode-native-tzdata-upgrade-2026c-2026d-2026c-2026d.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 d0a139cc46f9818bf05cb1c0f7b10d4cb48cc1fa Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Fri, 18 Sep 2026 05:10:26 +0000 Subject: [PATCH] tzcode-native,tzdata: upgrade 2026c -> 2026d,2026c -> 2026d MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Source: NEWS Release 2026d - 2026-09-11 15:21:07 -0700 Briefly: Canada’s Northwest Territories moved to permanent -06 on 2026-08-21. Obsolescent settings like TZ="EST5EDT" now conform better to POSIX. Fix security, performance and porting bugs in zic and localtime. Changes to future timestamps Canada’s Northwest Territories will not fall back on 2026-11-01 and will stay on -06 year-round, matching Alberta’s recent change. Model this with its traditional abbreviation CST. Although the change to permanent -06 legally took place on 2026-08-21, temporarily model the change to occur on 2026-11-01 at 02:00 for the same reason as other recent temporary hacks. (Caution: see “NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA” below.) This affects only America/Inuvik as the rest of the territory is covered by America/Edmonton, for which the equivalent change was released in 2026c. Changes to past timestamps Colombia’s 1992-05-02 spring forward was at 00:00, not 24:00. Iran’s 1979-05-26 spring forward was at 00:00, not 24:00. (Thanks to N.F. Hase.) The backward-compatibility names EST5EDT, CST6CDT, MST7MDT, and PST8PDT now conform better to POSIX. For example, EST5EDT now always uses the abbreviation "EST" for standard time (now always 5 hours behind UT) and "EDT" for daylight saving time, whereas it formerly had different UT offsets before standard time was introduced and sometimes used abbreviations like "LMT", "EWT" and "EPT", all contrary to POSIX. Also, though not required by POSIX these names now use US federal rules rather than rules of places like New York, reverting to 2024a behavior. This change affects only timestamps before 1966-10-30 at 01:00 standard time. Other data changes The temporary hacks used for North American timekeeping changes now work around a libstdc++ std::chrono bug in GCC 14.1-14.4, 15.1-15.2, and 16.1; see GCC bug 124851. This data change does not affect TZif files or timestamps. The change does not work around the related but less serious GCC bugs 116110 and 124513. These GCC bugs are all fixed in GCC 16.2. Changes to code zic now rejects Link targets that would have invalid names, and more efficiently processes Expires, Leap and Rule lines with years far in the past or future. (Thanks to Darren Carreras.) zic now ports to systems that report lack of link support via EINVAL, ENOSYS or EPERM errno values. (Thanks to Tom Lane.) When tzset and related functions encounter a TZif file that is too large for them, they now consistently fail instead of sometimes silently ignoring excess parts of the file. localtime-related functions no longer mishandle extreme timestamps when given TZif files holding some unlikely timezone histories. (Problem reported by David Sarkisyan.) localtime-related functions no longer check the values o [Changelog truncated as it exceeds 3000 characters; the full changelog can be found in an attachment to the AUH email] Source: NEWS Release 2026d - 2026-09-11 15:21:07 -0700 Briefly: Canada’s Northwest Territories moved to permanent -06 on 2026-08-21. Obsolescent settings like TZ="EST5EDT" now conform better to POSIX. Fix security, performance and porting bugs in zic and localtime. Changes to future timestamps Canada’s Northwest Territories will not fall back on 2026-11-01 and will stay on -06 year-round, matching Alberta’s recent change. Model this with its traditional abbreviation CST. Although the change to permanent -06 legally took place on 2026-08-21, temporarily model the change to occur on 2026-11-01 at 02:00 for the same reason as other recent temporary hacks. (Caution: see “NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA” below.) This affects only America/Inuvik as the rest of the territory is covered by America/Edmonton, for which the equivalent change was released in 2026c. Changes to past timestamps Colombia’s 1992-05-02 spring forward was at 00:00, not 24:00. Iran’s 1979-05-26 spring forward was at 00:00, not 24:00. (Thanks to N.F. Hase.) The backward-compatibility names EST5EDT, CST6CDT, MST7MDT, and PST8PDT now conform better to POSIX. For example, EST5EDT now always uses the abbreviation "EST" for standard time (now always 5 hours behind UT) and "EDT" for daylight saving time, whereas it formerly had different UT offsets before standard time was introduced and sometimes used abbreviations like "LMT", "EWT" and "EPT", all contrary to POSIX. Also, though not required by POSIX these names now use US federal rules rather than rules of places like New York, reverting to 2024a behavior. This change affects only timestamps before 1966-10-30 at 01:00 standard time. Other data changes The temporary hacks used for North American timekeeping changes now work around a libstdc++ std::chrono bug in GCC 14.1-14.4, 15.1-15.2, and 16.1; see GCC bug 124851. This data change does not affect TZif files or timestamps. The change does not work around the related but less serious GCC bugs 116110 and 124513. These GCC bugs are all fixed in GCC 16.2. Changes to code zic now rejects Link targets that would have invalid names, and more efficiently processes Expires, Leap and Rule lines with years far in the past or future. (Thanks to Darren Carreras.) zic now ports to systems that report lack of link support via EINVAL, ENOSYS or EPERM errno values. (Thanks to Tom Lane.) When tzset and related functions encounter a TZif file that is too large for them, they now consistently fail instead of sometimes silently ignoring excess parts of the file. localtime-related functions no longer mishandle extreme timestamps when given TZif files holding some unlikely timezone histories. (Problem reported by David Sarkisyan.) localtime-related functions no longer check the values o [Changelog truncated as it exceeds 3000 characters; the full changelog can be found in an attachment to the AUH email] --- meta/recipes-extended/timezone/timezone.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-extended/timezone/timezone.inc b/meta/recipes-extended/timezone/timezone.inc index 4860f00c8a..c63bb6f9f8 100644 --- a/meta/recipes-extended/timezone/timezone.inc +++ b/meta/recipes-extended/timezone/timezone.inc @@ -6,7 +6,7 @@ SECTION = "base" LICENSE = "BSD-3-Clause AND LicenseRef-PD" LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba" -PV = "2026c" +PV = "2026d" SRC_URI = "http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode;subdir=tz \ http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;subdir=tz \ @@ -14,5 +14,5 @@ SRC_URI = "http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz S = "${UNPACKDIR}/tz" -SRC_URI[tzcode.sha256sum] = "b1cffc3ace4c4c7cd0efba2f7add86ec3d0b79da48bcf03582671fd3c8feace8" +SRC_URI[tzcode.sha256sum] = "2f5c9f7fe29e6b8cb863583667884b8ce17b0a485355a054b591c6bdfcd81791" SRC_URI[tzdata.sha256sum] = "e4a178a4477f3d0ea77cc31828ff72aa38feff8d61aa13e7e99e142e9d902be4"