Revert 2023b’s data changes · eggert/tz@0e0b0eb github.com

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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fpipermail%2Ftz%2Fattachments%2F20230323%2Fb810bf1a%2F0001-Lebanon-springs-forward-later-this-year.patch&data=05%7C01%7Csitani%40aub.edu.lb%7C1e7473d2ac0649eabbad08db2bf004c9%7Cc7ba5b1a41b643e9a1206ff654ada137%7C1%7C0%7C638152082098334350%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Gv9OpWTw6e8IkZyIsIQ9RhntmvA8guMBYn0XL%2Brl1ZQ%3D&reserved=0>, 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).