From: Denys Dmytriyenko <denis@denix.org>
To: Armin Kuster <akuster808@gmail.com>
Cc: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: Re: [V2][PATCH 2/2] tzdata: update 2017c
Date: Thu, 26 Oct 2017 08:45:28 -0400 [thread overview]
Message-ID: <20171026124528.GV9221@denix.org> (raw)
In-Reply-To: <1508936236-9456-2-git-send-email-akuster808@gmail.com>
On Wed, Oct 25, 2017 at 05:57:16AM -0700, Armin Kuster wrote:
> LICENSE changed to to rewording
"due to"
> https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a
>
> Briefly:
> Northern Cyprus switches from +03 to +02/+03 on 2017-10-29.
> Fiji ends DST 2018-01-14, not 2018-01-21.
> Namibia switches from +01/+02 to +02 on 2018-04-01.
> Sudan switches from +03 to +02 on 2017-11-01.
> Tonga likely switches from +13/+14 to +13 on 2017-11-05.
> Turks & Caicos switches from -04 to -05/-04 on 2018-11-04.
> A new file tzdata.zi now holds a small text copy of all data.
> The zic input format has been regularized slightly.
>
> Changes to future time stamps
>
> Northern Cyprus has decided to resume EU rules starting
> 2017-10-29, thus reinstituting winter time.
>
> Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously
> predicted. (Thanks to Dominic Fok.) Adjust future predictions
> accordingly.
>
> Namibia will switch from +01 with DST to +02 all year on
> 2017-09-03 at 02:00. This affects UT offsets starting 2018-04-01
> at 02:00. (Thanks to Steffen Thorsen.)
>
> Sudan will switch from +03 to +02 on 2017-11-01. (Thanks to Ahmed
> Atyya and Yahia Abdalla.) South Sudan is not switching, so
> Africa/Juba is no longer a link to Africa/Khartoum.
>
> Tonga has likely ended its experiment with DST, and will not
> adjust its clocks on 2017-11-05. Although Tonga has not announced
> whether it will continue to observe DST, the IATA is assuming that
> it will not. (Thanks to David Wade.)
>
> Turks & Caicos will switch from -04 all year to -05 with US DST on
> 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04
> at 02:00. (Thanks to Steffen Thorsen.)
>
> Changes to past time stamps
>
> Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03.
> (Thanks to Arthur David Olson.)
>
> Detroit did not observe DST in 1967.
>
> Use railway time for Asia/Kolkata before 1941, by switching to
> Madras local time (UT +052110) in 1870, then to IST (UT +0530) in
> 1906. Also, treat 1941-2's +0630 as DST, like 1942-5.
>
> Europe/Dublin's 1946 and 1947 fallback transitions occurred at
> 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.)
>
> Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to
> American time in 1892, not 1879. (Thanks to Michael Deckers.)
>
> Adjust the 1867 transition in Alaska to better reflect the
> historical record, by changing it to occur on 1867-10-18 at 15:30
> Sitka time rather than at the start of 1867-10-17 local time.
> Although strictly speaking this is accurate only for Sitka,
> the rest of Alaska's blanks need to be filled in somehow.
>
> Fix off-by-one errors in UT offsets for Adak and Nome before 1867.
> (Thanks to Michael Deckers.)
>
> Add 7 s to the UT offset in Asia/Yangon before 1920.
>
> Changes to zone names
>
> Remove Canada/East-Saskatchewan from the 'backward' file, as it
> exceeded the 14-character limit and was an unused misnomer anyway.
>
> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
> meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} (97%)
>
> diff --git a/meta/recipes-extended/tzdata/tzdata_2017b.bb b/meta/recipes-extended/tzdata/tzdata_2017c.bb
> similarity index 97%
> rename from meta/recipes-extended/tzdata/tzdata_2017b.bb
> rename to meta/recipes-extended/tzdata/tzdata_2017c.bb
> index 55e8976..9e5b929 100644
> --- a/meta/recipes-extended/tzdata/tzdata_2017b.bb
> +++ b/meta/recipes-extended/tzdata/tzdata_2017c.bb
> @@ -2,15 +2,15 @@ SUMMARY = "Timezone data"
> HOMEPAGE = "http://www.iana.org/time-zones"
> SECTION = "base"
> LICENSE = "PD & BSD & BSD-3-Clause"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=ef1a352b901ee7b75a75df8171d6aca7"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
>
> DEPENDS = "tzcode-native"
>
> SRC_URI = "http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata"
> UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones"
>
> -SRC_URI[tzdata.md5sum] = "50dc0dc50c68644c1f70804f2e7a1625"
> -SRC_URI[tzdata.sha256sum] = "f8242a522ea3496b0ce4ff4f2e75a049178da21001a08b8e666d8cbe07d18086"
> +SRC_URI[tzdata.md5sum] = "1e751e7e08f8b68530674f04619d894d"
> +SRC_URI[tzdata.sha256sum] = "d6543f92a929826318e2f44ff3a7611ce5f565a43e10250b42599d0ba4cbd90b"
>
> inherit allarch
>
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2017-10-26 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 12:57 [V2][PATCH 1/2] tzcode-native: update to 2017c Armin Kuster
2017-10-25 12:57 ` [V2][PATCH 2/2] tzdata: update 2017c Armin Kuster
2017-10-26 12:45 ` Denys Dmytriyenko [this message]
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=20171026124528.GV9221@denix.org \
--to=denis@denix.org \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.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