Created attachment 1477696 [details] The offending calendar invite Description of problem: A Calendar invite for a recurring event sent from Lotus Notes (or similar) is meant to recur. It does not. Instead, it only displays once. Version-Release number of selected component (if applicable): 3.28.5 (3.28.5-1.fc28) How reproducible: 100% - importing the calendar invite into a new calendar also doesn't work Steps to Reproduce: 1. Import attached ics calendar 2. See that it appears on April 4th 2018 3. See that it doesn't recur afterwards Actual results: Get up 2hrs earlier than you needed to, as the cancellation of the earlier calendar event didn't work either. Expected results: Usual time lost due to meeting rather than 3x that. Additional info: I have edited out the sensitive data from the ics file, hopefully correctly.
Thanks for a bug report. The component contains RECURRENCE-ID, which means, at least for evolution, that it doesn't reference a recurring event, but one instance of that recurring event only. The exact line is: RECURRENCE-ID;RANGE=THISANDFUTURE:20180403T210000Z while the RANGE parameter is meant to overcome that [1], it is not used by the libecal/evolution that way. When you remove the RECURRENCE-ID before importing, you get the whole series. [1] https://tools.ietf.org/html/rfc5545#section-3.2.13
(In reply to Milan Crha from comment #1) > Thanks for a bug report. The component contains RECURRENCE-ID, which means, > at least for evolution, that it doesn't reference a recurring event, but one > instance of that recurring event only. The exact line is: > > RECURRENCE-ID;RANGE=THISANDFUTURE:20180403T210000Z > > while the RANGE parameter is meant to overcome that [1], it is not used by > the libecal/evolution that way. When you remove the RECURRENCE-ID before > importing, you get the whole series. > > [1] https://tools.ietf.org/html/rfc5545#section-3.2.13 Would this be considered a bug in the libecal/evolution code and one that should be fixed in stable versions? This is (however unfortunate it is) the "iCal" being produced by a product.
Yes, I'm thinking of moving this upstream, but I'm also afraid how many changes it'll require and how many things would eventually break, because it seems to me that many parts of the code (both on the evolution-data-server and evolution itself) consider anything with RECURRENCE-ID as an instance, not talking that it cannot work with it properly, it ignores/strips/replaces the RANGE value: https://gitlab.gnome.org/GNOME/evolution-data-server/blob/master/src/calendar/libecal/e-cal-component.c#L3824
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.