https://bugs.meego.com/show_bug.cgi?id=22594
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |1.2 --- Comment #1 from pohly <[email protected]> 2011-08-10 10:57:07 UTC --- commit c50b45865c5c271b1d3d26cdeb938b8d48f12d0a Author: Patrick Ohly <[email protected]> Date: Wed Aug 10 12:43:44 2011 +0200 CalDAV: transform UTC RECURRENCE-ID for Evolution (BMC #22594) Evolution shows a meeting twice on the day of a modified recurrence, if the meeting series was originally created and modified in Exchange, then imported into Google Calendar. The reason is that the RECURRENCE-ID in that case ends up being in UTC, even if the parent event has a time zone. Evolution and/or libical seem to have a bug here, IMHO they should recognize that the RECURRENCE-ID time is the same. SyncEvolution now works around this by transforming the UTC RECURRENCE-ID time into the time zone of the DTSTART time of the parent event. This is combined with removal of X-LIC-ERRORS into a new fixIncomingCalendar() method which needs to be called whenever a complete VCALENDAR is received from the CalDAV server (adding data from a report, GET). This transformation changes the "rid" part of the item IDs. It should be okay in a two-way sync (remove one sub item, add another) and a slow sync (libsynthesis recognizes the times as equal). -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: RESOLVED Who: [email protected] Assigned To: [email protected] Target Build: 1.2 Flags: Changed: Status Resolution Target Milestone -------- https://bugs.meego.com/show_bug.cgi?id=22594 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
