[tz] make traditional_tarballs fails on macOS for 2022b

[Deborah Goldsmith]

OK, I checked New York, London, Rome, Madrid, and Jakarta; there were no differences in the output from zdump. Also, I verified that the changes in America/Santiago were as expected. So I think there’s not a problem.

If you’re curious, I have an app that does binary diffs (Hex Fiend) and looking through New York, it looks like single byte values being changed by +1 or -1 here and there (which fits your point about numbering), plus two 6-byte deletions (or insertions, I can’t tell which is which since the files have the same name). The six byte sequences look like this:

B9B00004FFFF
B9B00008FFFF

Based on this testing, I think you can go ahead with 2022c; I can build real zoneinfo files and they appear to be correct.

Thanks,
Debbie

> On Aug 12, 2022, at 11:33 AM, Deborah Goldsmith via tz <tz at iana.org> wrote:
> 
> It’s not the version of zic; I get the same changes when I built with the old zic. So something in the input has changed, but it seems harmless. I will spot-check some more of the unexpectedly changed zones.
> 
> Thanks,
> Debbie
> 
>> On Aug 12, 2022, at 11:22 AM, Paul Eggert <eggert at cs.ucla.edu> wrote:
>> 
>> On 8/12/22 11:09, Deborah Goldsmith wrote:
>>> OK, I compared the two different versions of New_York and the transitions are identical. Could anything have changed about the binary format?
>> 
>> Yes, TZif form is not completely determined by the input (e.g., time types can be renumbered) so it's quite possible for two TZif files to have identical effects even though they're not byte-for-byte the same.
>