Hi Johan, it was a bug, here is the fix (for 0.10.0.4): http://www.inf-it.com/fixes/cdz_r_fix.diff steps to apply it: - copy the file into the caldavzap directory - use: patch -p1 < cdz_r_fix.diff - update cache: ./cache_update.sh JM p.s.: please report if it fixes your problem On 02 Apr 2014, at 13:28, Johan Vromans <jvromans@squirrel.nl> wrote:
Marten Gajda <marten@dmfs.org> writes:
I presume both VEVENTS are enclosed in the same VCALENDAR object, are they?
Yes, they are.
That's correct behavior. In this case both events *must* have the same UID because it's essentially the same event (just with an exception). The exception instance has a RECURRENCE-ID to specify the exact instance of the event that is replaced by the exception.
Ok, good to hear...
Then the next question is: why does CalDAVzap show *both* occurrences (the original one @09:30 and the modified one @10:30)?
-- Johan