| Age | Commit message (Collapse) | Author |
|
Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.
GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH
Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2023cgtz/tzdata2023cgtz.tar.gz
Summary of changes in tzdata2023c (2023-03-28 12:42:14 -0700):
This essentially reverts the 2023b update, as the proposed delay
of the start of summer time in Lebanon didn't end up happening as
intended. What did happen was apparently chaos ... the official
start of summer time was still delayed, but only until last Wednesday
night (between 2023-03-29 and 2029-03-30) - which has already passed.
Since it is unclear what local time was actually observed during
the period between when summer time was originally planned to start
(last Sat night, between 2023-03-25 and 2023-03-26) and when it
officially did, for now, this update simply reverts to the original
start time (2023-03-26 00:00:00 local). Should that turn out to
be sub-optimal, a later update can correct it. Only timestamps
for the period between 2023-03-26 00:00:00 and 2023-03-30 00:00:00
are affected.
|
|
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2023bgtz/tzdata2023bgtz.tar.gz
Summary of changes in tzdata2023b (2023-03-23 19:50:38 -0700):
* This year Lebanon starts summer time on April 20/21 not March 25/26.
|
|
|
|
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2023agtz/tzdata2023agtz.tar.gz
Summary of changes in tzdata2023a (2023-03-22 12:39:33 -0700):
* Starting in 2023, Egypt will observe DST from April's last Friday
through October's last Thursday.
* In 2023 Morocco's summer time start transition after Ramadan
will occur April 23, not April 30.
* This year Palestine will delay the start of summer time from
March 25 to April 29 due to Ramadan.
* Much of Greenland, represented by America/Nuuk, will continue to
observe DST using European Union rules.
* America/Yellowknife has changed from a Zone to a backward
compatibility Link, as it no longer differs from America/Edmonton
since 1970.
* Changes to commentary.
|
|
all, and I am simply unable to read or comprehend (properly).
|
|
(this one came from the gtz fork, rather than some local botch...)
|
|
I will work out why this doesn't happen automatically. Ugh.
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2022ggtz/tzdata2022ggtz.tar.gz
Summary of changes in tzdata2022g (2022-11-29 08:58:31 -0800):
* In the Mexican state of Chihuahua, the border strip near the US
will change to agree with nearby US locations on 2022-11-30.
* Much of Greenland, represented by America/Nuuk, stops observing
winter time after March 2023, so its daylight saving time becomes
standard time.
* Changes for pre-1996 northern Canada (thanks to Chris Walton):
* Merge America/Iqaluit and America/Pangnirtung into the former,
with a backward compatibility link for the latter name.
* Cambridge Bay, Inuvik, Iqaluit, Rankin Inlet, Resolute and
Yellowknife did not observe DST in 1965, and did observe DST
from 1972 through 1979.
* Whitehorse moved from -09 to -08 on 1966-02-27, not 1967-05-28.
* Colombia's 1993 fallback was 02-06 24:00, not 04-04 00:00.
* Singapore's 1981-12-31 change was at 16:00 UTC (23:30 local time),
not 24:00 local time.
Zones added by this update:
America/Ciudad_Juarez
|
|
got missed. This is in preparation for an updata to tzdata2022g
which is coming soon (still from the gtz fork).
There is a (small) chance this update might break the build, that will
be fixed (if it happens) when 2022g is merged (which should not be
very far into the future).
|
|
release, but didn't make it into the tzdata2022fgtz fork that
we use - and nor did the original zone data come back.
Links seem adequate for these (and were all some of them ever were).
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2022fgtz/tzdata2022fgtz.tar.gz
Summary of changes in tzdata2022f (2022-10-28 18:04:57 -0700):
* Mexico will no longer observe DST after 2022, except for areas
near the US border that continue to observe US DST rules.
* Fiji will not observe DST in 2022/3.
* Simplify four Ontario zones, as most of the post-1970 differences
seem to have been imaginary.
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2022egtz/tzdata2022egtz.tar.gz
Summary of changes in tzdata2022e (2022-10-11 11:13:02 -0700):
* Jordan and Syria are abandoning the DST regime and are changing to
permanent +03, so they will not fall back from +03 to +02 on
2022-10-28.
* On 1922-01-01 Tijuana adopted standard time at 00:00, not 01:00.
|
|
These are gone as separate zones, but the names should remain.
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download/2022dgtz/tzdata2022dgtz.tar.gz
Summary of changes in tzdata2022d (2022-09-23 12:02:57 -0700):
* Palestine now springs forward and falls back at 02:00 on the
first Saturday on or after March 24 and October 24, respectively.
* Simplify three Ukraine zones to one, since the post-1970
differences seem to have been imaginary.
This is an update from 2022b to 2022d, there were no tzdata changes in 2022c
|
|
in addition to the older (Eggert) version. The GTZ vesion is the one
we're currently using, so automating its use helps.
While here, correctly compare version numbers, correctly handling the
almost unthinkable need for a multi-char suffix after the year as the
version ID. This was almost correct before, but would have failed in
the case that 9999za was being updated to 10000a
And add the ability (should not be needed often) to fetch one version
but claim to be using another (this was useful this time, as 2022c
followed quickly on the heels of 2022b - but made no changes at all
to the data, just some of the build infrastructure we don't use).
The GTZ version hadn't been updated (there was no real need, since the
data, which is all that it alters, had not changed) at the time, so
we updated to 2022c using the gtz data file for 2022b. (The 2022cgtz
data file now exists - but didn't then).
|
|
|
|
https://github.com/JodaOrg/global-tz/releases/download//2022bgtz/tzdata2022bgtz.tar.gz
Summary of changes in tzdata2022c (2022-08-15 17:47:18 -0700):
* None.
Summary of changes in tzdata2022b (2022-08-10 15:38:32 -0700):
* Chile's 2022 DST start is delayed from September 4 to September 11.
* Iran plans to stop observing DST permanently, after it falls back
on 2022-09-21.
* From fall 1994 through fall 1995, Shanks wrote that Crimea's
DST transitions were at 02:00 standard time, not at 00:00.
* Iran adopted standard time in 1935, not 1946.
* Chile's observance of -04 from 1946-08-29 through 1947-03-31 was
considered DST, not standard time.
* Some old, small clock transitions have been removed, as people at
the time did not change their clocks.
|
|
years now) format (wording) that is used there, rather than that which
preceded it. With this we get the intended "what changed" in the generated
CVS commit message, rather than lots of emptiness.
|
|
|
|
|
|
|
|
moved back into the main data repo (restoring old data)
|
|
|
|
not from ftp://ftp.iana.org/tz/releases/tzdata2022agtz.tar.gz
(2022a comes from ftp://ftp.iana.org/tz/releases/tzdata2022a.tar.gz)
Note that 2022agtz is mechanically derived from 2022a by moving back
zone data from the "backzone" file that had been removed as "redundant"
(because differences to some other zone are all prior to 1970) so that
this pre 1970 data is restored. It isn't necessarily correct in all
cases, but it is usually better than using some other zone's data which
is just as likely to be incorrect for where it applies, and more so elsewhere.
Summary of changes in tzdata2022a (2022-03-15 23:02:01 -0700):
* Palestine will spring forward on 2022-03-27, not 2022-03-26.
* From 1992 through spring 1996, Ukraine's DST transitions were at
02:00 standard time, not at 01:00 UTC.
* Chile's Santiago Mean Time and its LMT precursor have been adjusted
eastward by 1 second to align with past and present law.
* Changes to commentary.
|
|
This includes 2021c (no changes) 2021d (Fiji change) 2021e (Palestine)
Fiji has cancelled summer time changes for 2021/2 summer. Currently
assume it will be back in 2022/3.
Palestine ends summer time October 29 01:00 (rather than Oct 30).
Pacific/Enderbury is renamed to Pacific/Kanton and updated for
historic data (Pacific/Enderbury retained as a link for compat).
Historic timestamp fixes for Niue, Rarotonga, Tongatapu
|
|
Samoa (Pacific/Apia) has cancelled summer time this year
(change effective last Sunday).
Jordan (Asia/Amman) has moved the start of summer time from
the last Thu/Fri in March to the last Thu/Fri in Feb
to begin next year (2022).
Some more of the non-controversial (and less important, mostly some
corrections to historical data) changes may follow soon.
|
|
GCC_NO_RETURN_LOCAL_ADDR are bugs in GCC itself, not the code.
|
|
remove an no longer relevant for gcc7 workaround (works fine in both
gcc9 and gcc 10.)
|
|
Do it properly and only enable thread-safety, but not the worker thread
support. The latter is what requires the whole libpthread dependency.
A potential compromis would be to use a weak pthread_create and only
enable worker threads if it is provided, but given that it is only
really used for large sorts, don't bother for now.
|
|
|
|
Summary of changes in tzdata2021a (2021-01-24 10:54:57 -0800):
South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
|
|
|
|
Release 2020f - 2020-12-29 00:17:46 -0800
No changes to tzdata, just to a part of the build procedure
not used on NetBSD
Release 2020e - 2020-12-22 15:14:34 -0800
Volgograd switched to Moscow time on 2020-12-27 at 02:00.
Correct many pre-1986 transitions, fixing entries originally
derived from Shanks. The fixes include changes to:
Australia, Bahamas, Bermuda, Belize, Ghana, Israel and Palestine,
Kenya and adjacent, Nigeria and adjacent, Seychelles, Vanuatu
Australia/Currie has been moved to the 'backward' file and its
corrected data moved to the 'backzone' file.
To better match legislation in Turks and Caicos, the 2015 shift to
year-round observance of -04 is now modeled as AST throughout before
returning to Eastern Time with US DST in 2018, rather than as
maintaining EDT until 2015-11-01.
|
|
Cherry-picked from upstream:
https://git.savannah.gnu.org/gitweb/?p=config.git;a=commit;h=1c4398015583eb77bc043234f5734be055e64bea
Everything except external/apache2/llvm/dist/llvm/cmake/config.guess
is patched, which is under vendor tag and cannot be modified. I expect
that this file is not actually used as we use hand-crafted version of
configure script instead of cmake for building LLVM.
Note that external/apache2/llvm/autoconf/autoconf/config.guess has
already been committed on Oct. 20, but commit message disappeared as
cvs aborted due to "permission denied" when trying to modify the file
mentioned above. Sorry for confusing you.
Also note that GMP uses its own config.guess Patch for
external/lgpl3/gmp/dist/config.guess is provided by ryo@. Thanks!
|
|
It is less trivial than expected and introduced some surprising breakage.
|
|
at least a few pkgsrc packages avoid base sqlite because it fails
this check, and it's probably a surprising performance penalty for
unsuspecting users
|
|
This has the advantage of not changing the number for non-vax, so is a
safer change for those architectures.
(Might not actually matter).
|
|
|
|
|
|
|