public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
* [PATCH]: update leapseconds
@ 2018-03-17 20:31 Gianni Tedesco
  2018-03-18 23:59 ` Paul Eggert
  0 siblings, 1 reply; 6+ messages in thread
From: Gianni Tedesco @ 2018-03-17 20:31 UTC (permalink / raw)
  To: libc-alpha

From 06b181c1370b368fc49ef3aede7e8ac7d47798c3 Mon Sep 17 00:00:00 2001
From: Gianni Tedesco <gianni@scaramanga.co.uk>
Date: Sun, 18 Mar 2018 05:21:56 +0900
Subject: [PATCH] Update leapseconds file per IERS Bulletein C 55

---
 timezone/leapseconds | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/timezone/leapseconds b/timezone/leapseconds
index d6343c0209..8b7b37a8b3 100644
--- a/timezone/leapseconds
+++ b/timezone/leapseconds
@@ -48,6 +48,9 @@ Leap	1997	Jun	30	23:59:60	+	S
 Leap	1998	Dec	31	23:59:60	+	S
 Leap	2005	Dec	31	23:59:60	+	S
 Leap	2008	Dec	31	23:59:60	+	S
+Leap	2012	Jun	30	23:59:60	+	S
+Leap	2015	Jun	30	23:59:60	+	S
+Leap	2016	Dec	31	23:59:60	+	S
 
 # INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS)
 #
@@ -56,13 +59,13 @@ Leap	2008	Dec	31	23:59:60	+	S
 # SERVICE DE LA ROTATION TERRESTRE
 # OBSERVATOIRE DE PARIS
 # 61, Av. de l'Observatoire 75014 PARIS (France)
-# Tel.      : 33 (0) 1 40 51 22 29
-# FAX       : 33 (0) 1 40 51 22 91
-# Internet  : services.iers@obspm.fr
+# Tel.      : 33 (0) 1 40 51 23 35
+# e-mail    : services.iers@obspm.fr
+# http://hpiers.obspm.fr/eop-pc
 #
-# Paris, 15 January 2009
+# Paris, 09 January 2018
 #
-# Bulletin C 37
+# Bulletin C 55
 #
 # To authorities responsible
 # for the measurement and
@@ -70,18 +73,18 @@ Leap	2008	Dec	31	23:59:60	+	S
 #
 # INFORMATION ON UTC - TAI
 #
-# NO positive leap second will be introduced at the end of June 2009.
+# NO leap second will be introduced at the end of June 2018.
 # The difference between Coordinated Universal Time UTC and the
 # International Atomic Time TAI is :		
 #
-# from 2009 January 1, 0h UTC, until further notice : UTC-TAI = -34 s
+# from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37 s
 #
 # Leap seconds can be introduced in UTC at the end of the months of December
 # or June,  depending on the evolution of UT1-TAI. Bulletin C is mailed every
 # six months, either to announce a time step in UTC, or to confirm that there
 # will be no time step at the next possible date.
 #
-# Daniel GAMBIS
-# Head			
+# Christian BIZOUARD
+# Director
 # Earth Orientation Center of the IERS
 # Observatoire de Paris, France
-- 
2.14.1

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH]: update leapseconds
  2018-03-17 20:31 [PATCH]: update leapseconds Gianni Tedesco
@ 2018-03-18 23:59 ` Paul Eggert
  2018-03-19  7:54   ` Gianni Tedesco
  2018-03-19 17:00   ` Joseph Myers
  0 siblings, 2 replies; 6+ messages in thread
From: Paul Eggert @ 2018-03-18 23:59 UTC (permalink / raw)
  To: Gianni Tedesco, libc-alpha

As I understand it, the leapseconds file (like most of the other files in the 
glibc timezone directory) is intended only for test data, and is not kept 
up-to-date. Perhaps this should be stated more clearly in the files' headers.

Another possibility would be to remove these files, as purposely out-of-date 
files cause confusion among glibc contributors.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH]: update leapseconds
  2018-03-18 23:59 ` Paul Eggert
@ 2018-03-19  7:54   ` Gianni Tedesco
  2018-03-19 17:00   ` Joseph Myers
  1 sibling, 0 replies; 6+ messages in thread
From: Gianni Tedesco @ 2018-03-19  7:54 UTC (permalink / raw)
  To: Paul Eggert, libc-alpha

On Sun, 2018-03-18 at 16:59 -0700, Paul Eggert wrote:
> As I understand it, the leapseconds file (like most of the other
> files in the 
> glibc timezone directory) is intended only for test data, and is not
> kept 
> up-to-date. Perhaps this should be stated more clearly in the files'
> headers.
> 
> Another possibility would be to remove these files, as purposely out-
> of-date 
> files cause confusion among glibc contributors.

Ah, I was under the impression they were used when converting in and
out of "right" timezones. But now I see that information is in the
tzinfo file itself.

My bad.

Gianni

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH]: update leapseconds
  2018-03-18 23:59 ` Paul Eggert
  2018-03-19  7:54   ` Gianni Tedesco
@ 2018-03-19 17:00   ` Joseph Myers
  2018-03-19 18:03     ` Gianni Tedesco
  1 sibling, 1 reply; 6+ messages in thread
From: Joseph Myers @ 2018-03-19 17:00 UTC (permalink / raw)
  To: Paul Eggert; +Cc: Gianni Tedesco, libc-alpha

On Sun, 18 Mar 2018, Paul Eggert wrote:

> As I understand it, the leapseconds file (like most of the other files in the
> glibc timezone directory) is intended only for test data, and is not kept
> up-to-date. Perhaps this should be stated more clearly in the files' headers.
> 
> Another possibility would be to remove these files, as purposely out-of-date
> files cause confusion among glibc contributors.

Maybe move them to e.g. timezone/test-sources?  (We already have 
timezone/testdata for *binary* timezone files used as test inputs to the 
timezone code, so it's probably a good idea to keep the different kinds of 
test inputs separate.)

-- 
Joseph S. Myers
joseph@codesourcery.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH]: update leapseconds
  2018-03-19 17:00   ` Joseph Myers
@ 2018-03-19 18:03     ` Gianni Tedesco
  2018-03-19 18:08       ` Joseph Myers
  0 siblings, 1 reply; 6+ messages in thread
From: Gianni Tedesco @ 2018-03-19 18:03 UTC (permalink / raw)
  To: Joseph Myers, Paul Eggert; +Cc: libc-alpha

On Mon, 2018-03-19 at 17:00 +0000, Joseph Myers wrote:
> On Sun, 18 Mar 2018, Paul Eggert wrote:
> 
> > As I understand it, the leapseconds file (like most of the other
> > files in the
> > glibc timezone directory) is intended only for test data, and is
> > not kept
> > up-to-date. Perhaps this should be stated more clearly in the
> > files' headers.
> > 
> > Another possibility would be to remove these files, as purposely
> > out-of-date
> > files cause confusion among glibc contributors.
> 
> Maybe move them to e.g. timezone/test-sources?  (We already have 
> timezone/testdata for *binary* timezone files used as test inputs to
> the 
> timezone code, so it's probably a good idea to keep the different
> kinds of 
> test inputs separate.)

Yeah, well, it's also getting shipped as part of the binary
distribution, at least on ubuntu, so if it's just test data then that's
weird...

Gianni

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH]: update leapseconds
  2018-03-19 18:03     ` Gianni Tedesco
@ 2018-03-19 18:08       ` Joseph Myers
  0 siblings, 0 replies; 6+ messages in thread
From: Joseph Myers @ 2018-03-19 18:08 UTC (permalink / raw)
  To: Gianni Tedesco; +Cc: Paul Eggert, libc-alpha

On Tue, 20 Mar 2018, Gianni Tedesco wrote:

> Yeah, well, it's also getting shipped as part of the binary
> distribution, at least on ubuntu, so if it's just test data then that's
> weird...

Distributions should be building from the separate tzdata package, not 
from glibc sources, which haven't installed the binary timezone data for 
several years.

-- 
Joseph S. Myers
joseph@codesourcery.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2018-03-19 18:08 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-17 20:31 [PATCH]: update leapseconds Gianni Tedesco
2018-03-18 23:59 ` Paul Eggert
2018-03-19  7:54   ` Gianni Tedesco
2018-03-19 17:00   ` Joseph Myers
2018-03-19 18:03     ` Gianni Tedesco
2018-03-19 18:08       ` Joseph Myers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).