Ah, ok. Thanks for the quick clarification! Cheers, Dave Rolsky http://blog.urth.org https://github.com/autarch On Sat, Dec 30, 2023 at 2:49 PM Paul Goyette <paul@whooppee.com> wrote:
On Sat, 30 Dec 2023, Dave Rolsky via tz wrote:
Hi all,
With the latest release (2023d) I'm seeing some surprising output from zdump for the Asia/Gaza & Asia/Hebron zones:
$> zdump -v Asia/Hebron ... Asia/Hebron Fri Mar 23 23:59:59 2068 UT = Sat Mar 24 01:59:59 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 24 00:00:00 2068 UT = Sat Mar 24 03:00:00 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 22:59:59 2068 UT = Sat Oct 20 01:59:59 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 23:00:00 2068 UT = Sat Oct 20 01:00:00 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 29 23:59:59 2069 UT = Sat Mar 30 01:59:59 2069 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 30 00:00:00 2069 UT = Sat Mar 30 03:00:00 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 22:59:59 2069 UT = Sat Oct 12 01:59:59 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 23:00:00 2069 UT = Sat Oct 12 01:00:00 2069 EET isdst=0 gmtoff=7200
This pattern of >2 transitions per year continues from that year.
Is this correct? It seems awfully weird.
IIRC, this is to accomodate a temporary-return-to-standard-time for the duration of Ramadan.
Cheers,
Dave Rolsky http://blog.urth.org https://github.com/autarch
!DSPAM:658fb40d15421143672522!
+---------------------+--------------------------+----------------------+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses: | | (Retired) | 1B11 1849 721C 56C8 F63A | paul@whooppee.com | | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoyette@netbsd.org | | & Network Engineer | | pgoyette99@gmail.com | +---------------------+--------------------------+----------------------+