GNOME Bugzilla – Bug 579965
adding an exception for a recurring meeting does not update LAST-MODIFIED, change is not synchronized with SyncEvolution
Last modified: 2009-08-07 08:15:56 UTC
Please describe the problem: Whenever an event is modified, its LAST-MODIFIED property should be set anew. SyncEvolution relies on this to find modified calendar items. When using "Remove this Occurrence", an EXDATE is added to the VEVENT, but it's LAST-MODIFIED is not updated. As a result this change is not synchronized by SyncEvolution. Steps to reproduce: 1. create a recurring event 2. save the event as iCalendar 2.0 3. use "Remove this Occurrence" in the Evolution calendar view 4. save again 5. compare LAST-MODIFIED Actual results: The LAST-MODIFIED is the same although the VEVENT is different. Expected results: The LAST-MODIFIED of the modified event should be higher. Does this happen every time? Yes. Other information: I have not verified whether this is a bug in the EDS backend or the GUI. My understanding is that the backend normally updates the LAST-MODIFIED, so I'm filing the bug here.
Created attachment 139629 [details] [review] Proposed patch to fix this issue I think I have found the reason and proposed this patch. The change is simple, just add update last-modified logic to calendar/file backend. I have tested, it works for me.
Created attachment 139631 [details] [review] Proposed patch to fix this issue I think I have found the reason and proposed this patch. The change is simple, just add update last-modified logic to calendar/file backend. I have tested, it works for me.
Created attachment 139630 [details] [review] Proposed patch to fix this issue I think I have found the reason and proposed this patch. The change is simple, just add update last-modified logic to calendar/file backend. I have tested, it works for me.
Sorry, network access for the web site seems extremely slow. Please ignore the triple patches, they are the same. (In reply to comment #3) > Created an attachment (id=139630) [edit] > Proposed patch to fix this issue > > I think I have found the reason and proposed this patch. > > The change is simple, just add update last-modified logic to calendar/file > backend. I have tested, it works for me. >
Please commit the patch.
(In reply to comment #5) > Please commit the patch. Congwu doesn't have commit rights and I have never tried to commit into the new git repo. Can you commit it yourself? If not, how do I commit? Push into master?
I committed the patch into master. It's not in 2.27.5, which was tagged earlier.