GNOME Bugzilla – Bug 349078
Hovd, Ulaanbaatar, Choibalsan is daylight saving
Last modified: 2013-09-14 16:49:54 UTC
Please describe the problem: Asia/Hovd, Asia/Ulaanbaatar, Asia/Choibalsan are in daylight saving timezone, but not in evolution-data-server, so people in these zones cannot check Adjust daylight saving timezone. Steps to reproduce: Apply patches to Hovd.ics, Ulaanbaatar.ics, Choibalsan.ics Actual results: You can use correct time when daylight saving Expected results: Does this happen every time? Other information:
Created attachment 69819 [details] [review] fixes daylight saving in Choibalsan timezone
Created attachment 69820 [details] [review] fixes daylight saving in Hovd.ics
Created attachment 69821 [details] [review] fixes daylight saving in Ulaanbaatar.ics
mongolia did not use DST in 1999 and 2000, i guess that's the reason for these wrong ics files. the patch corrects the missing time zone information, but then appointments in 1999 and 2000 would be wrong by one hour. :-/
*** Bug 348257 has been marked as a duplicate of this bug. ***
Note: Please see bug 348257 for some discussion about this issue.
libical lives in e-d-s, moving over. Can we please get approval for these patches?
Oops, forgot to inherit the Target Milestone. 1.7. Go go go! :)
chen: *poke* libical neither lives in e-d-s nor evo. i moved it to evo as there is a libical component. we should probably move the libical component to e-d-s because libical gets copied there, yeah.
Please commit the patch to cvs HEAD and gnome-2-14 branch.
Committed the patch to gnome-2-14 and HEAD branches on behalf of dulmandakh.
Thanks, chen. (In reply to comment #9) > libical neither lives in e-d-s nor evo. i moved it to evo as there is a libical > component. we should probably move the libical component to e-d-s because > libical gets copied there, yeah. Well, what I was about WRT "living" simply is, where libical is located inside the Evo stack. Which is e-d-s, hence the product change. Regarding libical living elsewhere and being an independant project... Well, since I figured this should go upstream, I had a look. Sadyl, it seems the latest libical release is years ago and actually what libical in Evo is based upon. There has been no upstream libical release ever since. Thus it is debateable, if it actually is living at all... ;) Anyway, I agree, the libical component should move from product evolution to e-d-s.
Setting attachment status appropriately. chen, *please* do care about this.
> Anyway, I agree, the libical component should move from product evolution to > e-d-s. > Done. The component libical now lives in EDS.
(in reference to comment #13:) nitpicking, anyway: guenther, chen *did* care about setting the attachment status appropriately. it was you who reset it. :-) fyi, i sometimes have the same problem with firefox not correctly reloading dropdown option menus.
Doh! I was sure that I forced a fresh reload (Shift Reload), as I always do in such cases. Anyway, I sure may have missed it here... Chen, sorry, I stand corrected with egg on my face. ;)