public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Alexander Marx <alexander.marx@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2] tzdata: Update to 2016d
Date: Thu, 21 Apr 2016 08:56:25 +0200	[thread overview]
Message-ID: <1461221785-5857-1-git-send-email-alexander.marx@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]

fixes: #11103

Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>

The 2016d release of the tz code and data is available. It reflects the
following changes, which were either circulated on the tz mailing list
or are relatively minor technical or administrative changes:

   Changes affecting future time stamps

     America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
     (Thanks to Alexander Krivenyshev for the heads-up.)

     Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
     (Thanks to Alexander Krivenyshev and Matt Johnson.)

     New zone Asia/Tomsk, split off from Asia/Novosibirsk. It covers
     Tomsk Oblast, Russia, which switches from +06 to +07 on 2016-05-29
     at 02:00.  (Thanks to Stepan Golosunov.)

   Changes affecting past time stamps

     New zone Europe/Kirov, split off from Europe/Volgograd.  It covers
     Kirov Oblast, Russia, which switched from +04/+05 to +03/+04 on
     1989-03-26 at 02:00, roughly a year after Europe/Volgograd made
     the same change.  (Thanks to Stepan Golosunov.)

     Russia and nearby locations had daylight-saving transitions on
     1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
     1992-03-28 at 23:00 and 1992-09-26 at 23:00.  (Thanks to Stepan
     Golosunov.)

     Many corrections to historical time in Kazakhstan from 1991
     through 2005.  (Thanks to Stepan Golosunov.)  Replace Kazakhstan's
     invented time zone abbreviations with numeric abbreviations.

Here are links to the release files:

   ftp://ftp.iana.org/tz/releases/tzcode2016d.tar.gz
   ftp://ftp.iana.org/tz/releases/tzdata2016d.tar.gz

The files are also available via HTTP as follows:

http://www.iana.org/time-zones/repository/releases/tzcode2016d.tar.gz
http://www.iana.org/time-zones/repository/releases/tzdata2016d.tar.gz

As usual, links to the latest release files are here:

http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz
http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz

   ftp://ftp.iana.org/tz/tzcode-latest.tar.gz
   ftp://ftp.iana.org/tz/tzdata-latest.tar.gz
---
 lfs/tzdata | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/tzdata b/lfs/tzdata
index 5cc3fc8..7f140c0 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2016a
+VER        = 2016d
 TZDATA_VER = $(VER)
 TZCODE_VER = $(VER)
 
@@ -45,8 +45,8 @@ objects = tzdata$(TZDATA_VER).tar.gz tzcode$(TZCODE_VER).tar.gz
 tzdata$(TZDATA_VER).tar.gz = $(DL_FROM)/tzdata$(TZDATA_VER).tar.gz
 tzcode$(TZCODE_VER).tar.gz = $(DL_FROM)/tzcode$(TZCODE_VER).tar.gz
 
-tzdata$(TZDATA_VER).tar.gz_MD5 = 0d3123eb1b453ec0620822bd65be4c42
-tzcode$(TZCODE_VER).tar.gz_MD5 = f5e0299925631da7cf82d8ce1205111d
+tzdata$(TZDATA_VER).tar.gz_MD5 = 14bf84b6c2cdab0a9428991e0150ebe6
+tzcode$(TZCODE_VER).tar.gz_MD5 = 06fc6fc111cd8dd681abdc5326529afd
 
 install : $(TARGET)
 
-- 
1.9.1


                 reply	other threads:[~2016-04-21  6:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1461221785-5857-1-git-send-email-alexander.marx@ipfire.org \
    --to=alexander.marx@ipfire.org \
    --cc=development@lists.ipfire.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