Bug 47468 - Sysinstall offers different timezones for Ukraine.
Summary: Sysinstall offers different timezones for Ukraine.
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 4.7-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-25 18:20 UTC by Igor Karpov
Modified: 2018-10-23 17:18 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Karpov 2003-01-25 18:20:06 UTC
	sysinstall offers different timezones for Ukraine, but there is only one timezone here, EET (Eastern Europe Time, [+0200]

Fix: 

Three additional timezones should be removed.
How-To-Repeat: 	Run /stand/sysinstall, choose Configure/Timezone/Europe/Ukraine
Comment 1 wollman 2003-01-25 21:48:38 UTC
<<On Sat, 25 Jan 2003 20:19:44 +0200, Igor Karpov <jc@minjust.gov.ua> said:

> 	sysinstall offers different timezones for Ukraine, but there
> is only one timezone here, EET (Eastern Europe Time, [+0200]

Actually, there are four timezones in Ukraine, all of which just
happen to observe the same legal time at present.  See
/usr/src/share/zoneinfo/europe.  Any issues with the time zone
database can be brought up with the database maintainers,
<tz@elsie.nci.nih.gov>; FreeBSD does not make local changes to it.
The maintainers would particularly appreciate any legal citations
specifically documenting the establishment of standard time in
Ukraine.

-GAWollman
Comment 2 Garrett Wollman freebsd_committer freebsd_triage 2003-01-25 21:49:00 UTC
State Changed
From-To: open->closed

Any issues must be resolved with database maintainers. 
FreeBSD does not make local changes.
Comment 3 Valentin Nechayev 2003-01-27 12:33:18 UTC
Four different Ukrainian timezones are reflections not of current timezone,
and not of official regulations, but of former ones in quite historical times.
One can see, e.g., comment for definition of Crimea time:

# Central Crimea used Moscow time 1994/1997.

Or for other two non-standard zones:

# Ruthenia used CET 1990/1991.
# Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991.

If it is subject for PR, the whole zonetime system is subject for PR because
it requires separate timezone to reflect any local time specific in any
past or future time. Moscow time in Crimea during 1994-1997 is fact.
It isn't our task to discuss its political reasonness or resonance.
It is question for timezone database maintainers to detect whether this base
should keep past time specifics. If yes, and there are disk space, each
request for reflecting local specific should be approved.
If no, one should delete all specifications which affects any day before
now, e.g., if now is 2003, any data for 2002 and earlier should be deleted.
Or, more moderate approach, delete all non-computer epoch (for Unix, before
1970). But this is -arch issue, or even Posix issue.

Hence I treat this PR as incorrect. Igor, I think you should discuss it in
-arch first.


=netch=
Comment 4 Igor Karpov 2003-01-27 13:41:01 UTC
On Mon, Jan 27, 2003 at 02:33:18PM +0200, Valentin Nechayev wrote:
> Four different Ukrainian timezones are reflections not of current timezone,
> and not of official regulations, but of former ones in quite historical times.
> One can see, e.g., comment for definition of Crimea time:
> 
> # Central Crimea used Moscow time 1994/1997.
> 
> Or for other two non-standard zones:
> 
> # Ruthenia used CET 1990/1991.
> # Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991.
> 
> If it is subject for PR, the whole zonetime system is subject for PR because
> it requires separate timezone to reflect any local time specific in any
> past or future time. Moscow time in Crimea during 1994-1997 is fact.
> It isn't our task to discuss its political reasonness or resonance.
> It is question for timezone database maintainers to detect whether this base
> should keep past time specifics. If yes, and there are disk space, each
> request for reflecting local specific should be approved.
> If no, one should delete all specifications which affects any day before
> now, e.g., if now is 2003, any data for 2002 and earlier should be deleted.
> Or, more moderate approach, delete all non-computer epoch (for Unix, before
> 1970). But this is -arch issue, or even Posix issue.
> 
> Hence I treat this PR as incorrect. Igor, I think you should discuss it in
> -arch first.

Agreed. Sounds like a question for arch-. But I'm talking only about
sysinstall behaiviour, not about timezone database itself.

BTW, I've found the official document on this matter. It's goverment
regulations number 509, May 13, 1996. In my poor translation it says:
"Time in Ukraine is set to second timezone (Kiev time). Each last Sunday
of March at 3am the time is changing to 4am and each last Sunday of
October the time at 4am is changing to 3am"

Regards,
-- 
Igor A. Karpov    phone: +380(44)238-0624
Unix System Administrator                   

		      "Cute" rots the intellect.
Comment 5 wollman 2003-01-27 15:03:02 UTC
<<On Mon, 27 Jan 2003 14:33:18 +0200, Valentin Nechayev <netch@netch.kiev.ua> said:

> Four different Ukrainian timezones are reflections not of current
> timezone, and not of official regulations, but of former ones in
> quite historical times.  One can see, e.g., comment for definition
> of Crimea time:

It is the objective of the database maintainers to maintain one entry
for every documented history of offsets-from-UTC for every country
since the beginning of the epoch (1970-01-01).  This is necessary in
order to be able to correctly process historical timestamps.

To the extent historical information is available for dates prior to
the beginning of the epoch, the database will also include it, but
will not break out separate zones for differing histories.

The FreeBSD Project defers to the design and maintenance decisions of
the (third-party) timezone database maintainers, who are recognized
experts on the topic.

I hope this makes matters clearer.

-GAWollman
Comment 6 mak1001 2018-10-23 17:18:24 UTC
And. Crimea - is not in russian federation.