[Syncevolution-issues] [Bug 22594] New: CalDAV: Google + Exchange + detached recurrences

https://bugs.meego.com/show_bug.cgi?id=22594 Summary: CalDAV: Google + Exchange + detached recurrences Classification: MeeGo Projects Product: SyncEvolution Platform: --- Version: unspecified Platform: Common Architecture: --- Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: patrick.ohly(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 BUILD IMAGE: SyncEvolution 1.1.99.5 BUG DETAILED DESCRIPTIONS =========================================================== Evolution shows detached recurrences twice. EXACT STEPS LEADING TO PROBLEM: =========================================================== 1. get your Google account invited to a meeting series from someone using Exchange 2. have the organizer modify (not delete!) one recurrence 3. sync with Evolution via CalDAV EXPECTED OUTCOME: =================== Regular meeting show except for the one modified recurrence, which must show the updated information. ACTUAL OUTCOME: =================== Evolution shows the meeting twice on the day of the modified recurrence. USER IMPACT: =================== Doesn't know which event is the up-to-date one. REPRODUCIBILITY: ===================================== 100% OTHER COMMENTS: =================== Occurs because the detached recurrence generated this way contains a RECURRENCE-ID in UTC. I suspect that this is legal according to the RFC and that there is an Evolution/libical bug here. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: NEW Who: patrick.ohly(a)intel.com Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- 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.