Not Kiev, it's Kyiv (Continuation of the question)

I would like to continue this topic - Not Kiev, it’s Kyiv.

The topic was closed, but the issue has not been fully resolved.

Set the “correct” time zone name
after.png
We perform the following sequence of actions:

  1. Uncheck “Time Zone Autodetect”
  2. Press “Apply”
  3. Check “Time Zone Autodetect”
  4. Press “Apply”

Result:
before.png
And one record:

15:29:51 echo: system,critical,info ntp change time Feb/16/2023 15:29:47 => Feb/16/2023 15:29:51

There was still some sequence of actions, that led to such an error. I can’t remember her yet.

Is the Kiev entry showing the wrong time?
https://en.wikipedia.org/wiki/Kyiv#Name

English: Kyiv (/ˈkiːjɪv/ KEE-yiv,[14] /kiːv/ KEEV[15]) or Kiev (/ˈkiːɛv/ KEE-ev)[16][17]

It turns out that this is not a “bug”, but a “feature”. :open_mouth:
I chose the name, hop - and it itself changed to another. :laughing:

The last tz version is still the “g” and is still present “Kiev” as alias, since Kyiv is present on later records, is used “Kiev” for auto set.

But since I do not think your router do not change country or time-zone so often, I think that auto-discovery is completely useless,
deplete uselessly the power, and must be disabled,
on this way you have the cosmetic “Kyiv” set, and you can stay all days to see that windows with right name inside.

For me, the database had to be corrected by removing definitely the old, obsolete, and of another culture version,
anyone Ukrainian looking for Kiev certainly understood that it was Kyïv (Київ) and NEVER Киев
It does nothing but occupy unnecessarily

Mikrotik does not maintain the TZ file, we just use it as it is.
There are two entries, for backwards compatibility (works like a shortcut to the other).
If you don’t like this, you can report to IANA.

Ok Normis… Let’s uncover the cards, the truth is that inside my message there is another message of solidarity dedicated to all Ukrainians…

It would be nice if the TZ database was somehow upgradeable separately (by uploading files downloaded from the IANA), even long after the latest RouterOS no longer supports the old hardware. Some of this old hardware may still be running when all of Europe finally gets their act together to stop DST (the issue was already discussed a few years ago but somehow got stuck).

Yes… but if you can update the database… you can simply disable DST and auto-detection.

For me the auto detection should turn itself off after the first use. And there’s no point in leaving it on unless the router “travels” all the time…
Just a waste of resources and power.

Mikrotik, what’s going on - my timezone is Kyiv, not Kiev. How can I choose my city, Kyiv?

V7 has periodic updates to the Linux TZ database used. V6 only gets security or other critical updates… But does seem it’s “Kyiv” in 6.49.14 (which came out recently).