On Mon, Sep 25, 2023 at 4:39 AM Vít Ondruch <vondruch(a)redhat.com> wrote:
Dne 22. 09. 23 v 16:01 Zbigniew Jędrzejewski-Szmek napsal(a):
> On Fri, Sep 22, 2023 at 10:43:05AM +0200, Vít Ondruch wrote:
>>
https://bugzilla.redhat.com/show_bug.cgi?id=2233281#c3
>>
>> This probably answers my question. So heads up to others.
>>
>> Dne 22. 09. 23 v 10:39 Vít Ondruch napsal(a):
>>> Was this implemented in past days? I am asking because this FTBFS
>>> suggest so:
>>>
>>>
https://koschei.fedoraproject.org/package/rubygem-timecop?collection=f40
> Yes. The change was done in rawhide a while ago, but it got pushed to F39
> only recently, see
https://bugzilla.redhat.com/show_bug.cgi?id=2233281#c3.
Dealing now with FTBFS rubygem- packages, the change proposal briefly
mentions: "In June of 2021, we proposed creating a new tzdata
sub-package that would only provide the UTC timezone.". I assume that
this have not happened, but I don't remember why and it seems that this
could be helpful.
In discussions with upstream IANA Tzdata and the Fedora developer
community in 2021, it was concluded that the consensus was to remove
tzdata entirely and fall back to UTC.
The noted problem was that any files provided by tzdata could be an
indication that all of tzdata is installed when that is not the case.
It was clearer to have no files installed and fallback to UTC or all
files installed and provide the full set of functionality.
Today, if a package needs UTC *and* more complex leap second
processing, then they need to install all of tzdata.
Cheers,
Carlos.