Red Hat Bugzilla – Bug 519638
Imported recurrent meeting not removed when deleting all occurrences
Last modified: 2013-10-06 21:32:25 EDT
Created attachment 358820 [details] Milan's patch from upstream bug 593023 Description of problem: Detached or imported meeting remain visible after deletion Version-Release number of selected component (if applicable): evolution-data-server-1.12.3-18 (but the problem is also current upstream) How reproducible: 100% reproducible Steps to Reproduce: 1. Create a recurrent meeting in Evolution 2. Save that meeting in an ics file 3. Reimport the meeting 4. Delete the meeting with "Delete All Occurrences" Actual results: The meeting remains visible and accessible in the calendar. Expected results: The meeting is removed from the calendar. Additional info: The meeting is removed internally though, as switching to another view back and forth will not display the meeting again. The problem might be related to the export/import as the other occurrences of the meeting are lost after reimporting the meeting. Milan has attached a patch for e-d-s in b.g.o 593023 that fixes the issue.
Created attachment 358821 [details] Example of recurrent meeting to import Just an example of meeting to import to reproduce the issue.
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.