Lebanon will not spring forward this weekend
On 3/23/23 09:42, Saadallah Itani wrote:
I had to send you the below as I am not subscribed to the list.
I'll quote the rest of your message below so list subscribers see it. Thank you for the info about Lebanon deciding today to not change its clocks this weekend. Ouch, this is very short notice. Since the March 25 transition was scheduled for 24:00 (i.e., midnight between March 25 and March 26) I assume this means the spring forward transition is will occur midnight between April 20 and April 21. I created the attached proposed patch to record this. Please let me know if this interpretation sounds correct to you. We'll need a new tzdb release soon, as tzdb 2023a becomes wrong around 51 hours from now.
On 23 Mar 2023, at 6:26 PM, Saadallah Itani <sitani@aub.edu.lb> wrote:
Hello,
Lebanon too announced today delay of Spring forward from March 25 to April 20.
preview.jpeg 960008904374 <https://imagescdn.mtv.com.lb/articles/960008904374.jpg?width=2000&quality=75> JPEG Image · 19 KB <https://imagescdn.mtv.com.lb/articles/960008904374.jpg?width=2000&quality=75>
<https://imagescdn.mtv.com.lb/articles/960008904374.jpg?width=2000&quality=75>
Regards, Saad Ext. 2229
Sent from my iPhone
Thank you Paul, patch seems legit. I hope Linux Vendors pull the new tzdb changes soon. Thanks Regards, Saad Ext. 2229 Sent from my iPhone
On 23 Mar 2023, at 8:48 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
On 3/23/23 09:42, Saadallah Itani wrote:
I had to send you the below as I am not subscribed to the list.
I'll quote the rest of your message below so list subscribers see it.
Thank you for the info about Lebanon deciding today to not change its clocks this weekend. Ouch, this is very short notice.
Since the March 25 transition was scheduled for 24:00 (i.e., midnight between March 25 and March 26) I assume this means the spring forward transition is will occur midnight between April 20 and April 21.
I created the attached proposed patch to record this. Please let me know if this interpretation sounds correct to you.
We'll need a new tzdb release soon, as tzdb 2023a becomes wrong around 51 hours from now.
On 23 Mar 2023, at 6:26 PM, Saadallah Itani <sitani@aub.edu.lb> wrote:
Hello,
Lebanon too announced today delay of Spring forward from March 25 to April 20.
preview.jpeg 960008904374 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimagescdn....> JPEG Image · 19 KB <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimagescdn....>
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimagescdn....>
Regards, Saad Ext. 2229
Sent from my iPhone
On 3/23/23 13:22, Saadallah Itani wrote:
I hope Linux Vendors pull the new tzdb changes soon.
We first have to publish tzdb 2023b with the patch for Lebanon <https://mm.icann.org/pipermail/tz/attachments/20230323/b810bf1a/0001-Lebanon...>, which I hope to do quite soon. Unfortunately, many GNU/Linux and other downstream suppliers take some time (a week or more) to test changes before they release data to their users. So unless you're using one of the smaller, faster-moving distros like Alpine Linux you'll likely be out of luck. People in Lebanon can work around the problem temporarily with an approximation like TZ='EET-2EEST,M4.3.5/0,M10.5.0/0' (this is good for predicted timestamps from April 15, 2022 up to but not including March 31, 2024). If your system doesn't support POSIX TZ strings (many cell phones are like this), you can instead use an approximation like TZ='Africa/Tripoli' (good for predicted timestamps from March 27, 2022 up to April 21 of this year).
participants (2)
-
Paul Eggert -
Saadallah Itani