https://bugs.kde.org/show_bug.cgi?id=313368
Bug ID: 313368
Summary: recurrence exceptions break syncing
Classification: Unclassified
Product: Akonadi
Version: 4.10
Hardware: Other
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: NOR
Component: Google Resource
Assignee: dvra...@redhat.com
Reporter: mollek...@kolabsys.com
CC: kdepim-bugs@kde.org
If I add an exception to a recurring event (i.e. make one recurrence a bit
longer than the rest), the google resource stops syncing. I assume this problem
is because the resource assumes UID's are unique (which they mostly are but not
always).
Recurrence exceptions are implemented as separate event with the same UID as
the original recurring event with an additional RecurrenceID to identify the
specific occurrence for which the exception applies.
This means the UID is not unique, the UID+RecurrenceID pair is though (in some
cases SEQUENCE has to be considered as well to guarantee uniqueness, but here
that shouldn't be a problem I think).
Note that this behavior is RFC compliant, so it's indeed a bug in the resource.
Also note that kcalcore doesn't really support exceptions yet (AFAIK), so
you'll have to use some kind of hack. I'll have to look into that for kolab as
well.
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
