Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: akuster808@gmail.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 12/13] tzcode: update to 2018f
Date: Mon, 22 Oct 2018 15:05:11 +0100	[thread overview]
Message-ID: <1540217112-24479-13-git-send-email-akuster808@gmail.com> (raw)
In-Reply-To: <1540217112-24479-1-git-send-email-akuster808@gmail.com>

 Changes to code

    zic now always generates TZif files where time type 0 is used for
    timestamps before the first transition.  This simplifies the
    reading of TZif files and should not affect behavior of existing
    TZif readers because the same set of time types is used; only
    their internal indexes may have changed.  This affects only the
    legacy zones EST5EDT, CST6CDT, MST7MDT, PST8PDT, CET, MET, and
    EET, which previously used nonzero types for these timestamps.

    Because of the type 0 change, zic no longer outputs a dummy
    transition at time -2**59 (before the Big Bang), as clients should
    no longer need this to handle historical timestamps correctly.
    This reverts a change introduced in 2013d and shrinks most TZif
    files by a few bytes.

    zic now supports negative time-of-day in Rule and Leap lines, e.g.,
    "Rule X min max - Apr lastSun -6:00 1:00 -" means the transition
    occurs at 18:00 on the Saturday before the last Sunday in April.
    This behavior was documented in 2018a but the code did not
    entirely match the documentation.

    localtime.c no longer requires at least one time type in TZif
    files that lack transitions or have a POSIX-style TZ string.  This
    future-proofs the code against possible future extensions to the
    format that would allow TZif files with POSIX-style TZ strings and
    without transitions or time types.

    A read-access subscript error in localtime.c has been fixed.
    It could occur only in TZif files with timecnt == 0, something that
    does not happen in practice now but could happen in future versions.

    localtime.c no longer ignores TZif POSIX-style TZ strings that
    specify only standard time.  Instead, these TZ strings now
    override the default time type for timestamps after the last
    transition (or for all time stamps if there are no transitions),
    just as DST strings specifying DST have always done.

    leapseconds.awk now outputs "#updated" and "#expires" comments,
    and supports leap seconds at the ends of months other than June
    and December.  (Inspired by suggestions from Chris Woodbury.)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
 .../tzcode/{tzcode-native_2018e.bb => tzcode-native_2018f.bb}     | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
 rename meta/recipes-extended/tzcode/{tzcode-native_2018e.bb => tzcode-native_2018f.bb} (70%)

diff --git a/meta/recipes-extended/tzcode/tzcode-native_2018e.bb b/meta/recipes-extended/tzcode/tzcode-native_2018f.bb
similarity index 70%
rename from meta/recipes-extended/tzcode/tzcode-native_2018e.bb
rename to meta/recipes-extended/tzcode/tzcode-native_2018f.bb
index 9a4e465..816e34d 100644
--- a/meta/recipes-extended/tzcode/tzcode-native_2018e.bb
+++ b/meta/recipes-extended/tzcode/tzcode-native_2018f.bb
@@ -11,10 +11,10 @@ SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz
 
 UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones"
 
-SRC_URI[tzdata.md5sum] = "97d654f4d7253173b3eeb76a836dd65e"
-SRC_URI[tzdata.sha256sum] = "6b288e5926841a4cb490909fe822d85c36ae75538ad69baf20da9628b63b692e"
-SRC_URI[tzcode.md5sum] = "c4d7df0fff7ba5588b32c5f27e2caf97"
-SRC_URI[tzcode.sha256sum] = "ca340cf20e80b699d6e5c49b4ba47361b3aa681f06f38a0c88a8e8308c00ebce"
+SRC_URI[tzdata.md5sum] = "e5e84f00f9d18bd6ebc8b1affec91b15"
+SRC_URI[tzdata.sha256sum] = "0af6a85fc4ea95832f76524f35696a61abb3992fd3f8db33e5a1f95653e043f2"
+SRC_URI[tzcode.md5sum] = "011d394b70e6ee3823fd77010b99737f"
+SRC_URI[tzcode.sha256sum] = "4ec74f8a84372570135ea4be16a042442fafe100f5598cb1017bfd30af6aaa70"
 
 S = "${WORKDIR}"
 
-- 
2.7.4



  parent reply	other threads:[~2018-10-22 14:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 14:04 [PATCH 00/13] Master package updates Armin Kuster
2018-10-22 14:05 ` [PATCH 01/13] nss: update to 3.39 includes CVE-2018-12384 Armin Kuster
2018-10-22 14:05 ` [PATCH 02/13] nspr: Update to 4.20 Armin Kuster
2018-10-23 13:41   ` Khem Raj
2018-10-22 14:05 ` [PATCH 03/13] gnutls: update to 2.6.4 Armin Kuster
2018-10-22 20:06   ` Andre McCurdy
2018-10-23  7:42     ` akuster808
2018-11-01 10:02       ` Andre McCurdy
2018-10-22 14:05 ` [PATCH 04/13] libpcre2: update to 10.32 Armin Kuster
2018-10-22 14:05 ` [PATCH 05/13] curl: update to 7.61.1 Armin Kuster
2018-10-22 14:05 ` [PATCH 06/13] openssh: Update to 7.9 primarily bug fixes Armin Kuster
2018-10-22 14:05 ` [PATCH 07/13] libsm: update to 1.2.3 Armin Kuster
2018-10-22 14:05 ` [PATCH 08/13] libx11: update to 1.6.7 and sytle cleanup Armin Kuster
2018-10-22 14:05 ` [PATCH 09/13] libxcb: update to 1.13.1 Armin Kuster
2018-10-22 14:05 ` [PATCH 10/13] xkeyboard-config: update to 2.25 Armin Kuster
2018-10-22 14:05 ` [PATCH 11/13] xf86-input-libinput: update to 0.28.1 Armin Kuster
2018-10-22 14:05 ` Armin Kuster [this message]
2018-10-22 14:05 ` [PATCH 13/13] tzdata: update to 2018f Armin Kuster
2018-10-22 14:33 ` ✗ patchtest: failure for Master package updates (rev3) Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1540217112-24479-13-git-send-email-akuster808@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox