maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Buenos Aires, Argentina time off by 1 hour|
|Product:||[Maemo Official Applications] Utilities||Reporter:||Jeff Moe <moe>|
|Status:||RESOLVED FIXED||QA Contact:||core-general-bugs|
SOFTWARE VERSION: Maemo 5 1.2009.42-11.002 EXACT STEPS LEADING TO PROBLEM: 1. Tap Clock 2. Add New World Clock for Buenos Aires, Argentina 3. Look at time it says it is. EXPECTED OUTCOME: The correct time for Buenos Aires, Argentina. ACTUAL OUTCOME: The time is off by one hour. The system thinks Buenos Aires is GMT -2, when it really is GMT -3. REPRODUCIBILITY: Always. OTHER COMMENTS: The time was *supposed* to change on Sunday October 18th, 2009. It didn't because the Argentina government, with zero foresight, decided against it *TWO DAYS BEFORE* on Friday October 16th, 2009. Total idiots. http://www.lanacion.com.ar/nota.asp?nota_id=1187055 You can check a site like this to see the correct time: http://www.timeanddate.com/worldclock/city.html?n=51 The same bug in Fedora and Debian FWIW: https://bugzilla.redhat.com/show_bug.cgi?id=529691 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551195 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20091105 Fedora/3.5.5-1.fc12 Firefox/3.5.5
thanks, the "bug" is actually of course in the system time zone data (ours of course was stale) this should be fixed in: glibc 2.5.1-1eglibc22+0m5 I'm not going to do the full marking bits because I don't know how they go, but I'm sure andre will come along and add them shortly :).
Debian had this fixed in 11 days. Fedora pushed an update *the same day* and had the update generally available the next day. Two days. Apparently this fix isn't even in PR1.1. This is a one-liner to fix. Nokia needs to realize that it can't push enormous drops of code on a single day every 6 months and keep pace. Incremental daily updates need to be done. Check how Debian/Fedora and every other major distribution do things. They do it this way for a reason...Learn it.
Agreeing, but a completely wrong place to post this and nobody will see it here.
This has been fixed in package glibc 2.5.1-1eglibc22+0m5 which is part of the internal build version 2009.51-5 (Note: 2009/2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).