info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1057099: bookworm-pu: package tzdata/2023c-5+deb12u1
0 views
Skip to first unread message
Aurelien Jarno
Nov 29, 2023, 1:00:04 PM11/29/23
to
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.d...@packages.debian.org
Usertags: pu
X-Debbugs-Cc: tzd...@packages.debian.org, debian...@lists.debian.org
Control: affects -1 + src:tzdata
[ Reason ]
tzdata contains a leap second file which is updated twice a year, and
which has an expiration date on 28 December 2023. Usually this file is
updated along with timezones changes, but 2023 has seen surprising low
number of timezone changes, and there hasn't been a new upstream version
since March! Therefore we need to do a specific upload to update this
file with only this change.
[ Impact ]
There is no leap second added at the end of 2023, so the impact is
relatively low, but NTP servers using this file usually emit warnings
28 days before the expiration date.
[ Tests ]
There is no test for this change.
[ Risks ]
The risk is quite low, the changes are minimal and routinely done twice
a year.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
This is the full changelog entry with explanations:
* Update leap-seconds.list from upstream
The leap-seconds.list change is taken from upstream, who took it from
NIST following an IERS Bulletin.
* Remove leapseconds during clean target
The cleanup of the leapseconds file, is needed as following the above
change, the one shipped in the upstream tarball do not match anymore the
one generated during build from leap-seconds.list. This is needed to
avoid a FTBFS after successful build.
[ Other info ]
Given the limited changes, I have already uploaded the package to the
archive. Thanks for considering.
Severity: normal
Tags: bookworm
User: release.d...@packages.debian.org
Usertags: pu
X-Debbugs-Cc: tzd...@packages.debian.org, debian...@lists.debian.org
Control: affects -1 + src:tzdata
[ Reason ]
tzdata contains a leap second file which is updated twice a year, and
which has an expiration date on 28 December 2023. Usually this file is
updated along with timezones changes, but 2023 has seen surprising low
number of timezone changes, and there hasn't been a new upstream version
since March! Therefore we need to do a specific upload to update this
file with only this change.
[ Impact ]
There is no leap second added at the end of 2023, so the impact is
relatively low, but NTP servers using this file usually emit warnings
28 days before the expiration date.
[ Tests ]
There is no test for this change.
[ Risks ]
The risk is quite low, the changes are minimal and routinely done twice
a year.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
This is the full changelog entry with explanations:
* Update leap-seconds.list from upstream
The leap-seconds.list change is taken from upstream, who took it from
NIST following an IERS Bulletin.
* Remove leapseconds during clean target
The cleanup of the leapseconds file, is needed as following the above
change, the one shipped in the upstream tarball do not match anymore the
one generated during build from leap-seconds.list. This is needed to
avoid a FTBFS after successful build.
[ Other info ]
Given the limited changes, I have already uploaded the package to the
archive. Thanks for considering.
0 new messages