Re: [ISSUE] [CLOSED] Leap second data in tzdata ‘right’ timezones considered invalid by coreutils and Chrony

[github-actions[bot] <github-actions[bot]@users.noreply.github.com>]

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

Closed issue by dpk on void-packages repository

https://github.com/void-linux/void-packages/issues/35715

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
Void 5.10.92_1 aarch64-musl Unknown uptodate rF
* package:  
tzdata-2021e_1
coreutils-8.32_4
chrony-4.2_1

### Expected behavior

```shell
$ TZ=right/UTC date -d 'Dec 31 2008 23:59:60'
Wed Dec 31 23:59:60 UTC 2008
```

(Test case from the chrony man page)

### Actual behavior

```
date: invalid date ‘Dec 31 2008 23:59:60’
```

This causes Chrony to reject the `leapsectz right/UTC` configuration directive, thus `CLOCK_TAI` on Void is always = UTC, at least when using Chrony. Presumably NTPd also doesn’t know where to get leap second data from, because there doesn’t seem to be any in Void.

The `/usr/share/zoneinfo/leapseconds` file I’ve seen on other systems is also missing, which could be related.