To follow up on renato's comment #5... we could simply convert back from UTC to localtime in indicator-datetime, but that will only work correctly if you're running in the same timezone where the alarm was created.
And in fact we're already making this mistake in the clock app:
1. create & save a new wakeup alarm to kick at 6am m-f
2. exit ubuntu-clock-app
3. kill all evolution processes to ensure everything in its cache gets flushed
4. change to another timezone
5. restart ubuntu-clock-app
6. result: the alarm no longer kicks at 6am
To follow up on renato's comment #5... we could simply convert back from UTC to localtime in indicator-datetime, but that will only work correctly if you're running in the same timezone where the alarm was created.
And in fact we're already making this mistake in the clock app:
1. create & save a new wakeup alarm to kick at 6am m-f
2. exit ubuntu-clock-app
3. kill all evolution processes to ensure everything in its cache gets flushed
4. change to another timezone
5. restart ubuntu-clock-app
6. result: the alarm no longer kicks at 6am