On 02/04/14 02:45, Patrick Ohly wrote: > * ical: workaround for libical 1.0 builtin timezone change > > libical 1.0 started to return VTIMEZONE definitions with multiple > absolute transition times instead of RRULEs. This causes problems when > exchanging data with peers (see > https://sourceforge.net/p/freeassociation/bugs/95/). > > In SyncEvolution, this affected sending an event using New Zealand > time in vCalendar 1.0 format to a phone, because the internal, > out-dated definition of the time zone in libsynthesis was used as > fallback when loading RRULE-based timezone definitions from libical > failed (see "[SyncEvolution] Some events showing wrong time on > phone"). It might also affect exchanging data with CalDAV peers (not > tested). > > The workaround is to include the original code from libical.
This bug appears to be fixed. I upgraded to the unstable version syncevolution and installed libical1.0 in place of libical0. Created and synced several events occurring during the problematic 3 week timeframe of the Pacific/Auckland timezone. All events synced correctly. Thank you Jane Atkinson _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
