Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. get an invitation via email
2. accept it into CalDAV calendar
when looking into the calendar via web UI, it's still in New state
event state changes to Accepted
Created attachment 523991 [details]
RHEL 2.28 dump
Created attachment 523992 [details]
F15 3.0.3 dump
Created attachment 524264 [details]
proposed evo patch
Evolution 3.0.3 provides a user email entry for a CalDAV calendar, which is used to add the attendee in a response for cases when it's missing. The 2.28.3 doesn't have it, and it adds an empty attendee with no address, which seems to be filtered out before the component is put through CalDAV backend to the server, as mine tests shows this empty attendee being added into the event.
This is the most I can do with 2.28.3 unless breaking too many things around CalDAV calendar setup. This ensures that there will never be used the empty address, but the default mail address is used for cases when the attendee wasn't found. The right fix will come to RHEL7.
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. If you would like it considered as an
exception in the current release, please ask your support
Hi Suzanne, I ask you to revisit the decision as patch is ready and it pre-tested by me (I use scratch build of evolution with this patch applied without problems). Thank you
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.