http://bugs.meego.com/show_bug.cgi?id=10906
Summary: Evolution Calendar: remove child event => extra EXDATE
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
Adding content verification to client-test
Client::Sync::ical20::testLinkedItemsRemoveNormal revealed a bug: when removing
the child event ("detached recurrence"), the expected outcome to have just the
original parent, as if the child had never existed.
Instead Evolution Data Server adds an "EXDATE" entry for the day when the child
recurred. This is a side effect of e_cal_remove_object_with_mod().
I consider the cure for this problem (replace e_cal_remove_object_with_mod()
with something like "remove all events, re-add only the relevant ones") worse
than the original problem.
To solve the nightly test failures I'll rather hack the test so that it adds
the EXDATE to the expected data in this particular case (easier than hacking
synccompare and more specific).
--
Configure bugmail: http://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
