Bug#849621: libc-bin: 'zdump -c' can't properly handle leap-second insertion at last second of year
using year limit boundaries of 2016 minimum (inclusive) and 2017 maximum (non-inclusive), then including 2018 maximum, yields:
$ zdump -V -c2016,2017 right/America/Denver | grep ':60 '
$ zdump -V -c2016,2018 right/America/Denver | grep ':60 '
right/America/Denver Sat Dec 31 23:59:60 2016 UT = Sat Dec 31 16:59:60 2016 MST isdst=0 gmtoff=-25200
$ zdump -V -c2016,2017 right/Etc/UTC | grep ':60 '
$ zdump -V -c2016,2018 right/Etc/UTC | grep ':60 '
right/Etc/UTC Sat Dec 31 23:59:60 2016 UT = Sat Dec 31 23:59:60 2016 UTC isdst=0 gmtoff=0
that extra leap second is getting ignored as being in 2016.
Certainly no big deal, and i added 'upstream' tag, as this is likely something missed in the upstream sources.
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libc-bin depends on:
ii libc6 2.19-18+deb8u7
libc-bin recommends no packages.
libc-bin suggests no packages.
-- Configuration Files:
/etc/ld.so.conf changed [not included]
-- no debconf information