[tz] Proposal to revert 2023b’s Lebanon data changes

Rany Hany rany_hany at riseup.net
Mon Mar 27 18:24:37 UTC 2023

Agree with the change, I don't think the government's decision to 
continue postponing DST until March 30 should be respected. This change 
most accurately reflects the reality in Lebanon (except for maybe one 
sector ATM) and does not violate the principle of least surprise when 

Thank you for cleaning up this mess :)

On 3/27/23 21:11, Paul Eggert via tz wrote:
> We need a new release soon to address the time zone chaos in Lebanon. 
> One option is to revert 2023b's data and go back to 2023a as I 
> suggested earlier. Another is to record the chaos in more detail in 
> the data. The attached proposed patch (which I installed into the 
> developmental repository on GitHub) takes the former approach, as I 
> expect the latter would cause more problems than it would cure. This 
> follows a similar (although not identical) precedent in Rio de Janeiro 
> in 1993.
> In short, the patch would make 2023c identical to 2023a except for 
> comments, which do not count as part of the data.
> It is a confusing and controversial situation. Comments welcome. In 
> the meantime I again suggest to downstream distributors to stick with 
> 2023a and avoid 2023b.

More information about the tz mailing list