Open javobalazs opened 5 years ago
maybe it is related to this: https://github.com/lau/tzdata/issues/79
There was a typo in tzdata from iana. that broke the parsing method and made impossible to create tzdata ets table, hence, no timezones are available.
Not related, although the bug is probably in tzdata (or it should be fixed in tzdata?), but this is my speculation. Perhaps someone who is knowledgeable in timex should point it out. If tzdata is the culprit, of course I will raise the issue there. Again, the specific problem is that in certain Unices time zone information is in different places where timex (or tzdata) expects it.
Not related, although the bug is probably in tzdata
It's not.
maybe it is related to this: lau/tzdata#79 There was a typo in tzdata from iana. that broke the parsing method and made impossible to create tzdata ets table, hence, no timezones are available.
It's not related to that. That only has to do with updating to new data, which happens in a separate process. Tzdata would just keep using the existing older data for time zones that ships with the tzdata hex package.
Hope this helps.
Thanks for the comment. The fundamental problem is with the timezone file of the operating system (the file that contains the local timezone). TrueOS puts it in a different place, and someone (either tzdata or timex, or even something else) doesn't pick that up. I don't know the mechanism how the local timezone info gets loaded in timex, and probably it would take ages to me to discover it, that's why I've posted here. Nevertheless, I discovered the root cause of the failure, see above.
Steps to reproduce
Description of issue
Workaround
Environment
The proper timezone had been configured to TrueOS with
tzsetup
, but this doesn't generate an/etc/timezone
file. This information is recorded in/var/db/zoneinfo
. Erlang and Elixir had been compiled from source. I usedelixir-1.8.1
andotp_src_21.2
.