From: "Cygwin tzcode/tzdata Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: tzcode, tzdata 2022c
Date: Sat, 20 Aug 2022 10:04:38 -0600 [thread overview]
Message-ID: <announce.20220820100438.10759-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* tzcode 2022c
* tzdata 2022c
The Time Zone Database (often called tz, tzdb, or zoneinfo) contains
data that represents the history of local time for many locations around
the world, and supports conversion of UTC time to local time at those
locations to allow display of those local times. It is updated
periodically to reflect changes made by political bodies to daylight
saving (summer time) rules, UTC offsets, and time zone boundaries.
The tzcode package provides the tzselect, zdump, and zic utilities.
For more details on changes, please see the announcement or below:
https://mm.icann.org/pipermail/tz-announce/2022-August/000072.html
Release 2022c 2022-08-15 17:47:18 -0700
Briefly:
* Work around awk bug in FreeBSD, macOS, etc.
* Improve tzselect on intercontinental Zones.
Changes to code
* Work around a bug in onetrueawk that broke commands like
'make traditional_tarballs' on FreeBSD, macOS, etc.
* Add code to tzselect that uses experimental structured comments in
zone1970.tab to clarify whether Zones like Africa/Abidjan and
Europe/Istanbul cross continent or ocean boundaries.
* Fix bug with 'zic -d /a/b/c' when /a is unwritable but the
directory /a/b already exists.
* Remove zoneinfo2tdf.pl, as it was unused and triggered false
malware alarms on some email servers.
reply other threads:[~2022-08-20 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=announce.20220820100438.10759-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).