http://bugzilla.opensuse.org/show_bug.cgi?id=1175548 http://bugzilla.opensuse.org/show_bug.cgi?id=1175548#c1 --- Comment #1 from Sven Teresniak <opensuse@zehnvierzig.org> --- Debian, Ubuntu, Alpine don't have a timezone package for java and use the tzdb.dat from the JDK/JRE. Fedora installs a timezone package as dependency but without Beijing (and without tz.properties - couldn't find how they managed to *not* use the JDKs tzdb) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175548 http://bugzilla.opensuse.org/show_bug.cgi?id=1175548#c3 Mark�ta Machov� <mmachova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmachova@suse.com --- Comment #3 from Mark�ta Machov� <mmachova@suse.com> --- Thanks for the info. What is more, the Beijing zone does not work (maybe due to some recent hacks, I don't know), see boo#1179871. Do we want to fix Beijing and keep it, or will we drop it? IMO it only confuses our users, although I see the point of it, so I would rather drop it. It would be nice if we decided it here to be able to mark the possible future bugs as duplicates of this one. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175548 Mark�ta Machov� <mmachova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|disabled_mmachova@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175548 http://bugzilla.opensuse.org/show_bug.cgi?id=1175548#c6 --- Comment #6 from Marguerite Su <i@marguerite.su> --- Hi, the old patch was introduced long ago (back to 2008? may be) I think it was related with SLE, because back in 2008, there's no openSUSE but SUSE Linux. SUSE has office in China and does business. China has Beijing as capital, and people use Beijing Time everywhere (the government and enterprises). No buyers want a system respect Beijing time while display the time as Shanghai? maybe that's the reason. (For new installation, YaST UI can choose Beijing and Shanghai, although they represent a same time) I do the link work because the original patch breaks the systemd timedatectl. that is, timedatectl display a wrong time, 00:00:00 instead of 08:00:00. I think this will not introduce problem any more, because "link" is allowed by timezone upstream. To talk about the removal, I personally don't have to the right to do that. I can help with the fix. but I don't think I can remove it. especially it may involve SUSE company, and I am Chinese myself :-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175548 http://bugzilla.opensuse.org/show_bug.cgi?id=1175548#c8 --- Comment #8 from Marguerite Su <i@marguerite.su> --- I myself is okay for the removal if I put my developer hat on. Because I know it is not standard. In Linux world, Fedora/Ubuntu/Arch Linux don���t have Asia/Beijing because by default timezone package does not ship it. But, the emotional part of me treats it as an outstanding feature of SUSE/openSUSE I work in Beijing, live in Beijing, just as many other SUSE employees/customers. I think it���s such ���engineering culture��� that make SUSE win the Chinese market :-) So I hesitate about this issue, I know if I can���t fix it I should let it go, but I hope someone could stand and fix it. Technically, this is a combination of bugs for Java language and chromium (downstream users for timezone package) 1. IANA will not take Asia/Beijing in any way because Asia/Shanghai is already Beijing time. 2. But timezone package does ���link��� everywhere to make sure every capital of any country can have a legal timezone name. Eg, North/South Korea and Japan are located in the same timezone (GMT+09:00), but IANA has Asia/Pyongyang, Asia/Seoul and Asia/Tokyo. So Asia/Beijing actually deserves and linking is the right fix at timezone package side But: 3. Java respects timezone package but then it introduces its own tzdb.dat and tzupdater tool :-) 4. Chromium reads timezone too but does a lot self hacks for time later -- You are receiving this mail because: You are on the CC list for the bug.