#112 Fedocal/Google Calendar inconsistency (DST change?)
Closed: Fixed None Opened 8 years ago by kparal.

I have created a new recurring event in Fedocal today, Fedora QA Meeting in the QA calendar. I defined it to New York timezone, because USA just switched to summer time and the event should be timed to USA local time.

The event looks OK in fedocal - it's stored as 11:00-12:00 New York, and displays as 16:00-17:00 Prague. In three weeks (when CET moves to CEST), it displays as 17:00-18:00 Prague. Very cool.

However, if I look at the same calendar at Google Calendar, I see it one hour later, i.e. 17:00-18:00 Prague today, and 18:00-19:00 Prague in three weeks.

Something is broken, maybe the ical export?

I have noticed lines like these in the ical export:
{{{
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
}}}

Maybe the problem is that some of the timezones are defined only till 2006?


hm, that's an interesting one.

If you change the UNTIL date to something more recent, does it change anything on google?

If you don't want to create a Google account, please try locally with Evolution, it exhibits the same behavior as Google Calendar. When I bumped up the UNTIL dates to year 2016, nothing changed.

Ok so the line
{{{
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
}}}
is in fact not related at all with the issue here.

Check the difference between:
{{{
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN

BEGIN:VTIMEZONE
TZID:EST

BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD

BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD

BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT

BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT

END:VTIMEZONE

BEGIN:VEVENT
UID:20140312T101603Z-5185@carmine.pingoured.fr
DTSTART;TZID=EST:20140309T090000
DTEND;TZID=EST:20140309T100000
ORGANIZER:pingou
SUMMARY:test full rec
END:VEVENT
END:VCALENDAR
}}}

and
{{{
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN

BEGIN:VTIMEZONE
TZID:TEST

BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD

BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD

BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT

BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT

END:VTIMEZONE

BEGIN:VEVENT
UID:20140312T101603Z-5185@carmine.pingoured.fr
DTSTART;TZID=TEST:20140309T090000
DTEND;TZID=TEST:20140309T100000
ORGANIZER:pingou
SUMMARY:test full rec
END:VEVENT
END:VCALENDAR
}}}

I think this is the source of the problem, but fixing it might be a little though :-/

Login to comment on this ticket.

Metadata