$ date && sudo hwclock
Sun Feb 3 17:53:30 EST 2013
Sun 03 Feb 2013 05:53:28 PM EST -0.582869 seconds
Hmmmm, I think it is I who is not following now.
I don't understand what you mean by " just relying on time zone data will not work if your hardware clock is already in local time." My hwclock is in local time and I get the proper value of -05 with date +%:z.
I believe that the timezone of the hwclock has no bearing on the bug with WakeUp. As rtc wakealarm only accepts times in UTC the only thing we are concerned with is the difference between the time the user wants the alarm set to (presumably expressed in their local time), and UTC time.
$ date && sudo hwclock
Sun Feb 3 17:53:30 EST 2013
Sun 03 Feb 2013 05:53:28 PM EST -0.582869 seconds
Hmmmm, I think it is I who is not following now.
I don't understand what you mean by " just relying on time zone data will not work if your hardware clock is already in local time." My hwclock is in local time and I get the proper value of -05 with date +%:z.
I believe that the timezone of the hwclock has no bearing on the bug with WakeUp. As rtc wakealarm only accepts times in UTC the only thing we are concerned with is the difference between the time the user wants the alarm set to (presumably expressed in their local time), and UTC time.