[tz] Fwd: Bulletin C number 69

No leap second 2025-06-30, per below. See attached patch. -- Tim Parenti -- Forwarded message - From: IERS EOP Product Center Date: Tue, 7 Jan 2025 at 05:00 Subject: Bulletin C number 69 To: INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE I

[tz] Re: Paraguay may adopt permanent DST soon

On Sat, 21 Dec 2024 at 07:50, Carlos Raúl Perasso via tz wrote: > But aren't we always asking for at least 6 months lead time for the > changes to propagate correctly? > Since September 2020 , our formal guidance has r

[tz] Re: localized date without time

On Wed, 12 Feb 2025 at 13:17, Brian Inglis via tz wrote: > Unfortunately date dislikes 24:00 While I used 24:00 here as that is more our common parlance, 23:59:59 was my original suggestion, and is broadly acceptable as a common stand-in in both technical and legal contexts. The resulting < vs

[tz] Re: Chile's Aysén Region might switch from -04/-03 to -03 on April 5

On Thu, 20 Mar 2025 at 10:58, Yonathan Dossow via tz wrote: > today we have more confirmation of the change. > > Aysen region will keep UTC-3 all year > Thanks; I've installed the attached patch, based heavily on Paul's earlier work, to the development repository. This obviously means we'll nee

[tz] Re: Paraguay Timezone change

On Mon, 24 Mar 2025 at 13:38, Martin Vuyk via tz wrote: > A lot of systems went crazy [in Paraguay] because some changed the > timezone [this past Saturday evening] and some didn't. I have some > headaches at work already on a Sunday (yay). AFAIK this database is the > source of truth for most sy

[tz] Re: Adjust to coverage of TZ America/Punta_Arenas

Thanks, Eduardo. We received media reports of this announcement and made this change on Thursday in https://github.com/eggert/tz/commit/ee73bc3a722d297495062b649abc849cfabd588c I have gone through and cleaned up some comments on the last ~10 years of Chilean legislation and updated links to Diar

[tz] Re: [PATCH] No need for America/Coyhaique in zonenow.tab

On Sun, 23 Mar 2025 at 11:51, Aldrin Martoq Ahumada via tz wrote: > Can we keep the newly created America/Coyhaique? Look carefully at this particular patch: It only removes reference to America/Coyhaique from zonenow.tab, a file which is explicitly designed to list one (and only one) row for e

[tz] Re: [PATCH] Don't mention boulder.nist.gov

On Fri, 18 Apr 2025 at 12:58, Brooks Harris via tz wrote: > So seems somebody updated that one from some other source? Such as: > https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list > Yes, tzdata started preferring and pulling directly from IERS in 2024, because (a) NIST was becoming inc

[tz] Re: [PATCH] Don't mention boulder.nist.gov

On Wed, 23 Apr 2025 at 05:30, Martin Burnicki via tz wrote: > According to the original specification presented by Judah Levine and > Dave Mills in 2000 (a copy can be found here: > http://time.kinali.ch/ptti/2000papers/paper34.pdf), > the file contains a special comment line starting with "#$",

[tz] Re: [PATCH] Don't mention boulder.nist.gov

On Fri, 18 Apr 2025 at 04:00, Collin Funk via tz wrote: > The generated leapseconds file mentions the data can be retrieved from > ftp.boulder.nist.gov/pub/time/leap-seconds.list, but the domain no > longer resolves. The domain definitely still resolves: $ dig ftp.boulder.nist.gov > <…snipped…

[tz] Re: DST offsets other than +1

On Mon, 3 Mar 2025 at 17:49, Paul Gilmartin via tz wrote: > On 3/3/25 15:20, Tim Parenti via tz wrote: > > ... > > A quick visual scan of the penultimate column shows that all such SAVE > values have an absolute value of either 0 or 1:00, apart from the Troll and >

[tz] Re: DST offsets other than +1

On Mon, 3 Mar 2025 at 16:01, Doug Ewell via tz wrote: > 2. Is there an easy way I could have looked up this information in the tz > files? > > (“Easy” means without exhaustively parsing all the Rule and Zone lines, as > a processor would have to do.) > Not sure if you count grep as a processor,

[tz] Re: Paraguay DST is no longer in use

The recent changes for Paraguay were incorporated in two commits (1 , 2 ) dated 2024-10-05 and 2024-10-15, and included in version 2025a which

[tz] Re: localized date without time

On Wed, 12 Feb 2025 at 03:53, Alejandro Colomar wrote: > Even if that's non-standard, as long as it's a valid GNU > date, I'm happy with it. I put much more detailed thoughts on both immediate-term fixes and longer-term suggestions on GitHub where they were first requested: https://github.com/s

[tz] Re: North Dakota HB 1259 requiring year-round standard time

On Tue, 11 Feb 2025 at 16:40, Paul Eggert via tz wrote: > Similar efforts are present in Utah…(for permanent standard time) Interestingly, it is Utah representative Celeste Maloy who has introduced a bill into this session of Congress to allow states to opt into year-round daylight time in the

[tz] Re: Maryland HB1290

On Fri, 21 Feb 2025 at 08:10, Arthur Olson via tz wrote: > The hearing on Maryland House Bill 1290, "Full-Year Daylight Saving Time," > has been cancelled: > Meanwhile, progress on Utah's bill for year-round standard time also appears to have halted… https://www.ksl.com/article/51256784/senators

[tz] Re: Request for Update: Iran's Official Time Zone – No Daylight Saving Time Since 2023

On Mon, 19 May 2025 at 19:20, Khalil Kharazi via tz wrote: > In March 2022, the Iranian Parliament passed legislation to permanently > abolish Daylight Saving Time (DST), effective from March 2023. As a result, > Iran now observes a fixed time zone of UTC+3:30 throughout the entire year, > with n

[tz] Re: PyCon US Time

On Mon, 19 May 2025 at 19:34, Ee Durbin via tz wrote: > PyCon US makes extensive use of software across an annoying number of > online and offline systems. These include GNU/Linux servers, PostgreSQL > databases, all web browsers, a mobile application, Raspberry Pis, iPads, > Zebra printers, prin

[tz] Re: Proposed correction for zone.tab and Link: Europe/Uzhgorod to Europe/Uzhhorod

On Thu, 15 May 2025 at 15:58, Sorel Si via tz wrote: > Currently, the city is referenced as "Uzhgorod" in `zone.tab` and as a > Link target: In `zone.tab`: UA +4837+02218 Europe/Uzhgorod Zakarpattya west > You appear to be working from an older (and possibly downstream-modified) version of tzdb.

[tz] Re: Proposal to Add Asia/Penampang to IANA Time Zone Database

On Thu, 29 May 2025 at 11:51, Doug Ewell via tz wrote: > That isn’t what tz identifiers are for. They represent regions that have > followed the same time zone rules (UTC offset, daylight-saving offset and > dates) since 1970. They are not intended to identify locations with > “distinct historica

[tz] Re: Issue with America/Nuuk tz

On Wed, 18 Jun 2025 at 20:08, Dan Juskevicius via tz wrote: > Using the latest release (2025b), I have been able to reproduce an issue > with America/Nuuk time where it reports at -02 instead of -01; I realize > that as of 2023-03-25 the America/Nuuk time zone changed its standard time > from -03

[tz] Fix example for zic transition coalescence

I noticed a typo in zic.8 within the "correct" example given for how zic handles/coalesces certain transitions. While I was there, it also made sense to expand a bit more on where the incorrect interpretation could come from, as a further nod to why we choose instead to have zic coalesce transitio

[tz] Re: TZif Version Selection Issue in tzcode2025b

On Wed, 11 Jun 2025 at 13:57, PATAN JEELAN BASHA via tz wrote: > Just one quick question—since TZif3 is available and is a newer format and > technically a higher version than TZif2. > is there a specific reason why the IANA time zone database continues to > use TZif2? Per tzfile.5, which descr

[tz] Fwd: Bulletin C number 70

No leap second 2025-12-31, per below. See attached patch. -- Tim Parenti -- Forwarded message - From: IERS EOP Product Center Date: Mon, 7 Jul 2025 at 05:43 Subject: Bulletin C number 70 To: INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE I