[evolution-data-server] [ECalMetaBackend] Removing detached instance doesn't set EXDATE



commit f164674c352b69658b8226248b1d1cb0280e56ce
Author: Milan Crha <mcrha redhat com>
Date:   Thu Aug 31 12:34:51 2017 +0200

    [ECalMetaBackend] Removing detached instance doesn't set EXDATE
    
    When removing a detached instance the master object should be updated
    too, with an EXDATE, otherwise the instance on that occurrence will
    reappear instead of being deleted.

 src/calendar/libedata-cal/e-cal-meta-backend.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/src/calendar/libedata-cal/e-cal-meta-backend.c b/src/calendar/libedata-cal/e-cal-meta-backend.c
index 159294a..e87f218 100644
--- a/src/calendar/libedata-cal/e-cal-meta-backend.c
+++ b/src/calendar/libedata-cal/e-cal-meta-backend.c
@@ -2050,7 +2050,9 @@ ecmb_remove_object_sync (ECalMetaBackend *meta_backend,
                        if (existing_comp != master_comp) {
                                instances = g_slist_remove (instances, existing_comp);
                                g_clear_object (&existing_comp);
-                       } else if (mod == E_CAL_OBJ_MOD_ONLY_THIS) {
+                       }
+
+                       if (existing_comp == master_comp && mod == E_CAL_OBJ_MOD_ONLY_THIS) {
                                success = FALSE;
                                g_propagate_error (error, e_data_cal_create_error (ObjectNotFound, NULL));
                        } else {


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]