[tz] leap_second.list not updated after latest IERS Bulletin C

Paul Eggert eggert at cs.ucla.edu
Fri Dec 15 18:55:28 UTC 2023

On 2023-12-15 01:31, Martin Burnicki wrote:

> I'm pretty sure they have no problem making the file "public domain" but 
> the question arises as to what wording should be used to express this in 
> a way that will be accepted by the TZ DB project.
> Has anyone ever suggested a formulation that meets the requirement of 
> the TZDB project, and told them why this was a requirement?

Yes, I suggested some wording in an email archived here:


The wording was:

#      This file is in the public domain.

and there was some explanation in that email. I vaguely recall 
corresponding with them directly around then, but don't remember details.

It sounds like you have better connections and so perhaps you could 
forward this email to them.

While we're on the topic, a few more suggestions:

* It'd be helpful if the file did not contain trailing white space, as 
that raises some red flags in some text editors and version control systems.

* The phrase "see the README file in the 'sources' directory" should be 
reworded so that the file can stand alone, e.g., by replacing it with 
the phrase "see <https://hpiers.obspm.fr/iers/bul/bulc/ntp/sources/README>".

* The file should suggest the more-secure HTTPS protocol instead of the 
less-secure FTP protocol.

Proposed patch attached (this patch does not recompute the hash code).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: leap-seconds.patch
Type: text/x-patch
Size: 6125 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/tz/attachments/20231215/9d1f28ed/attachment.bin>

More information about the tz mailing list