Bug#1012191: tzdata: /usr/share/zoneinfo/leap-seconds.list will expire on 2022-06-28 in Debian OldStable 10.x/Buster

Dave Ewart

unread,

May 31, 2022, 3:20:03 PM5/31/22

to

Package: tzdata
Version: 2021a-0+deb10u3
Severity: normal

ntpd has begun reporting that /usr/share/zoneinfo/leap-seconds.list is
approaching expiry (28 June 2022):

>> May 31 15:17:20 [...] ntpd[25270]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 28 days

Is there an updated package with updated expiry date available?

This bug is with 'oldstable', I'm unclear whether I would expect this package to
be updated or not any more.

-- System Information:
Debian Release: 10.12
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-20-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii debconf [debconf-2.0] 1.5.71+deb10u1

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
tzdata/Zones/Arctic:
tzdata/Zones/SystemV:
tzdata/Zones/Australia:
tzdata/Zones/Antarctica:
tzdata/Zones/Indian:
tzdata/Zones/Asia:
tzdata/Zones/Etc:
tzdata/Zones/America:
* tzdata/Areas: Europe
tzdata/Zones/Africa:
* tzdata/Zones/Europe: London
tzdata/Zones/Pacific:
tzdata/Zones/Atlantic:
tzdata/Zones/US:

Patrik Schindler

unread,

Jun 1, 2022, 4:30:03 AM6/1/22

to

This bug currently appears also with Bullseye on some dozens of installs for me.

Paul Slootman

unread,

Jun 8, 2022, 10:30:03 AM6/8/22

to

severity 1012191 important
thanks

The time is ticking, and the leap second data is now due to expire in 20
days.

There is a 2022a-1 version in testing. Could this be included in
bullseye-updates and perhaps buster-updates? I've downloaded it manually
and it seems fine in bullseye.

Thanks,
Paul

Aurelien Jarno

unread,

Jun 9, 2022, 3:00:03 PM6/9/22

to

control: tag -1 + confirmed

On 2022-06-08 16:08, Paul Slootman wrote:
> severity 1012191 important
> thanks
>
> The time is ticking, and the leap second data is now due to expire in 20
> days.

An update is planned before the deadline.

> There is a 2022a-1 version in testing. Could this be included in
> bullseye-updates and perhaps buster-updates? I've downloaded it manually
> and it seems fine in bullseye.

No you do not want to do that. 2022a-1 includes changes we might not
want in a stable update.

Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aure...@aurel32.net http://www.aurel32.net

Dave Ewart

unread,

Jun 21, 2022, 11:30:04 AM6/21/22

to

This bug has been closed but there is still no update in the oldstable
repository as far as I can see.

# dpkg -l|grep tzdata
ii tzdata 2021a-0+deb10u3 all time zone and daylight-saving time data

# grep zoneinfo /var/log/syslog
Jun 21 15:17:20 equinox ntpd[25270]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 7 days

Have I missed something or is this update still waiting to hit the
repository?

Dave.

--
Dave Ewart, da...@sungate.co.uk

signature.asc

gregor herrmann

unread,

Jun 21, 2022, 11:40:03 AM6/21/22

to

On Tue, 21 Jun 2022 16:21:07 +0100, Dave Ewart wrote:

> This bug has been closed but there is still no update in the oldstable
> repository as far as I can see.
>
> # dpkg -l|grep tzdata
> ii tzdata 2021a-0+deb10u3 all time zone and daylight-saving time data

That's not the repository but your local installation :)

% rmadison tzdata
tzdata | 2018e-0+deb8u1 | oldoldoldstable | source, all
tzdata | 2020a-0+deb9u1 | oldoldstable | source, all
tzdata | 2021a-0+deb10u3 | oldstable | source, all
tzdata | 2021a-0+deb10u5 | buster-updates | source, all
tzdata | 2021a-0+deb10u5 | oldstable-proposed-updates | source, all
tzdata | 2021a-1+deb11u2 | stable | source, all
tzdata | 2021a-1+deb11u4 | proposed-updates | source, all
tzdata | 2021a-1+deb11u4 | stable-updates | source, all
tzdata | 2022a-1 | testing | source, all
tzdata | 2022a-1 | unstable | source, all

So you have 2021a-0+deb10u3 from oldstable installed, and the fixed
version 2021a-0+deb10u5 is in buster-updates, which you seem to miss
in your sources.list.

(I assume it will end up in oldstable proper in the next point
release but for inbetween updates, {old}stable-updates is needed.)

Cheers,
gregor

--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-

signature.asc

Dave Ewart

unread,

Jun 21, 2022, 2:40:03 PM6/21/22

to

On Tuesday, 21.06.2022 at 17:29 +0200, gregor herrmann wrote:

> On Tue, 21 Jun 2022 16:21:07 +0100, Dave Ewart wrote:
>
> > This bug has been closed but there is still no update in the oldstable
> > repository as far as I can see.
> >
> > # dpkg -l|grep tzdata
> > ii tzdata 2021a-0+deb10u3 all time zone and daylight-saving time data
>
> That's not the repository but your local installation :)
>
> % rmadison tzdata
> tzdata | 2018e-0+deb8u1 | oldoldoldstable | source, all
> tzdata | 2020a-0+deb9u1 | oldoldstable | source, all
> tzdata | 2021a-0+deb10u3 | oldstable | source, all
> tzdata | 2021a-0+deb10u5 | buster-updates | source, all
> tzdata | 2021a-0+deb10u5 | oldstable-proposed-updates | source, all
> tzdata | 2021a-1+deb11u2 | stable | source, all
> tzdata | 2021a-1+deb11u4 | proposed-updates | source, all
> tzdata | 2021a-1+deb11u4 | stable-updates | source, all
> tzdata | 2022a-1 | testing | source, all
> tzdata | 2022a-1 | unstable | source, all
>
> So you have 2021a-0+deb10u3 from oldstable installed, and the fixed
> version 2021a-0+deb10u5 is in buster-updates, which you seem to miss
> in your sources.list.
>
> (I assume it will end up in oldstable proper in the next point
> release but for inbetween updates, {old}stable-updates is needed.)

I know that's my version, I was simply trying to demonstrate (perhaps
poorly) that the updated version hadn't reached my system. :-)

I have never used the 'updates' or 'proposed-updates' for a production
stable system because my understanding is that those repositories were
not necessary, nor recommended, for a purely 'stable' installation.
"Don't add extra repositories" etc.

I see the point you're making: will have to make an exception here, I
guess.

Thanks,

signature.asc

gregor herrmann

unread,

Jun 21, 2022, 3:10:03 PM6/21/22

to

On Tue, 21 Jun 2022 19:26:35 +0100, Dave Ewart wrote:

> > So you have 2021a-0+deb10u3 from oldstable installed, and the fixed
> > version 2021a-0+deb10u5 is in buster-updates, which you seem to miss
> > in your sources.list.
> >
> > (I assume it will end up in oldstable proper in the next point
> > release but for inbetween updates, {old}stable-updates is needed.)
>
> I know that's my version, I was simply trying to demonstrate (perhaps
> poorly) that the updated version hadn't reached my system. :-)

I'm sorry if the tongue-in-cheek aspect of my reply wasn't clear
enought :)

> I have never used the 'updates' or 'proposed-updates' for a production
> stable system because my understanding is that those repositories were
> not necessary, nor recommended, for a purely 'stable' installation.
> "Don't add extra repositories" etc.

Well, (old)stable-update is just an intermediate step for packages on
their way to a point release which might be needed earlier than the
latter ist happening.

Cf. https://wiki.debian.org/StableUpdates

(which explicitly mentions "timezone data")

> I see the point you're making: will have to make an exception here, I
> guess.

It does indeed make sense, in my experience.

signature.asc