diff -Nru tzdata-2023b/asia tzdata-2023c/asia --- tzdata-2023b/asia 2023-03-23 19:45:11.000000000 +0100 +++ tzdata-2023c/asia 2023-03-28 00:14:40.000000000 +0200 @@ -2693,9 +2693,37 @@ # Lebanon # # From Saadallah Itani (2023-03-23): -# Lebanon too announced today delay of Spring forward from March 25 to April 20. -# From Paul Eggert (2023-03-23): +# Lebanon ... announced today delay of Spring forward from March 25 to April 20. +# +# From Paul Eggert (2023-03-27): +# This announcement was by the Lebanese caretaker prime minister Najib Mikati. # https://www.mtv.com.lb/en/News/Local/1352516/lebanon-postpones-daylight-saving-time-adoption +# A video was later leaked to the media of parliament speaker Nabih Berri +# asking Mikati to postpone DST to aid observance of Ramadan, Mikati objecting +# that this would cause problems such as scheduling airline flights, to which +# Berri interjected, "What flights?" +# +# The change was controversial and led to a partly-sectarian divide. +# Many Lebanese institutions, including the education ministry, the Maronite +# church, and two news channels LCBI and MTV, ignored the announcement and +# went ahead with the long-scheduled spring-forward on March 25/26, some +# arguing that the prime minister had not followed the law because the change +# had not been approved by the cabinet. Google went with the announcement; +# Apple ignored it. At least one bank followed the announcement for its doors, +# but ignored the announcement in internal computer systems. +# Beirut international airport listed two times for each departure. +# Dan Azzi wrote "My view is that this whole thing is a Dumb and Dumber movie." +# Eventually the prime minister backed down, said the cabinet had decided to +# stick with its 1998 decision, and that DST would begin midnight March 29/30. +# https://www.nna-leb.gov.lb/en/miscellaneous/604093/lebanon-has-two-times-of-day-amid-daylight-savings +# https://www.cnbc.com/2023/03/27/lebanon-in-two-different-time-zones-as-government-disagrees-on-daylight-savings.html +# +# Although we could model the chaos with two Zones, that would likely cause +# more trouble than it would cure. Since so many manual clocks and +# computer-based timestamps ignored the announcement, stick with official +# cabinet resolutions in the data while recording the prime minister's +# announcement as a comment. This is how we treated a similar situation in +# Rio de Janeiro in spring 1993. # # Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule Lebanon 1920 only - Mar 28 0:00 1:00 S @@ -2719,11 +2747,13 @@ Rule Lebanon 1989 only - May 10 0:00 1:00 S Rule Lebanon 1990 1992 - May 1 0:00 1:00 S Rule Lebanon 1992 only - Oct 4 0:00 0 - -Rule Lebanon 1993 2022 - Mar lastSun 0:00 1:00 S +Rule Lebanon 1993 max - Mar lastSun 0:00 1:00 S Rule Lebanon 1993 1998 - Sep lastSun 0:00 0 - Rule Lebanon 1999 max - Oct lastSun 0:00 0 - -Rule Lebanon 2023 only - Apr 21 0:00 1:00 S -Rule Lebanon 2024 max - Mar lastSun 0:00 1:00 S +# This one-time rule, announced by the prime minister first for April 21 +# then for March 30, is commented out for reasons described above. +#Rule Lebanon 2023 only - Mar 30 0:00 1:00 S + # Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Asia/Beirut 2:22:00 - LMT 1880 2:00 Lebanon EE%sT diff -Nru tzdata-2023b/debian/changelog tzdata-2023c/debian/changelog --- tzdata-2023b/debian/changelog 2023-03-24 14:24:54.000000000 +0100 +++ tzdata-2023c/debian/changelog 2023-03-29 12:47:49.000000000 +0200 @@ -1,3 +1,12 @@ +tzdata (2023c-0ubuntu0.22.10.0) kinetic; urgency=medium + + * New upstream version (LP: #2012599): + - Revert all changes made in 2023b to model this week's daylight saving + chaos in Lebanon. + * Add autopkgtest test case for 2023c release + + -- Benjamin Drung Wed, 29 Mar 2023 12:47:49 +0200 + tzdata (2023b-0ubuntu0.22.10.0) kinetic; urgency=medium * New upstream version (LP: #2012599): diff -Nru tzdata-2023b/debian/tests/python tzdata-2023c/debian/tests/python --- tzdata-2023b/debian/tests/python 2023-03-24 14:24:41.000000000 +0100 +++ tzdata-2023c/debian/tests/python 2023-03-29 12:46:57.000000000 +0200 @@ -100,11 +100,11 @@ date = datetime.datetime(2023, 4, 28, 12, 0, tzinfo=tzinfo) self.assertEqual(self._hours(date.utcoffset()), 3) - def test_2023b(self) -> None: - """Test Lebanon delays DST from 2023b release.""" + def test_2023c(self) -> None: + """Test Lebanon's reverted DST delay from 2023c release.""" tzinfo = zoneinfo.ZoneInfo("Asia/Beirut") date = datetime.datetime(2023, 4, 2, tzinfo=tzinfo) - self.assertEqual(self._hours(date.utcoffset()), 2) + self.assertEqual(self._hours(date.utcoffset()), 3) def main() -> None: diff -Nru tzdata-2023b/NEWS tzdata-2023c/NEWS --- tzdata-2023b/NEWS 2023-03-24 03:51:51.000000000 +0100 +++ tzdata-2023c/NEWS 2023-03-28 21:43:45.000000000 +0200 @@ -1,14 +1,19 @@ News for the tz database -Release 2023b - 2023-03-23 19:50:38 -0700 +Release 2023c - 2023-03-28 12:42:14 -0700 + + Changes to past and future timestamps + + Model Lebanon's DST chaos by reverting data to tzdb 2023a. + (Thanks to Rany Hany for the heads-up.) - Briefly: - Lebanon delays the start of DST this year. + +Release 2023b - 2023-03-23 19:50:38 -0700 Changes to future timestamps This year Lebanon springs forward April 20/21 not March 25/26. - (Thanks to Saadallah Itani.) + (Thanks to Saadallah Itani.) [This was reverted in 2023c.] Release 2023a - 2023-03-22 12:39:33 -0700 diff -Nru tzdata-2023b/version tzdata-2023c/version --- tzdata-2023b/version 2023-03-24 03:51:52.000000000 +0100 +++ tzdata-2023c/version 2023-03-28 21:43:46.000000000 +0200 @@ -1 +1 @@ -2023b +2023c