CompEditor sets DTSTAMP incorrectly
#1521 (closed) describes a case, where data uploaded by evoltion has DTSTAMP and LAST-MODIFIED fields. The DTSTAMP and LAST-MODIFIED fields have different values.
The calendar object is not scheduled (has no ORGANIZER and ATTENDEE at the same time). As not scheduled calendar object PUT on CalDAV the calendar object has no METHOD.
Per https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.7.2 the DTSTAMP and LAST-MODIFIED must be the same, if there is no METHOD. My reading is, that for not scheduled objects, LAST-MODIFIED is redundant.
In the case of an iCalendar object that doesn't specify a "METHOD" property, this property (DTSTAMP) is equivalent to the "LAST-MODIFIED" property.
In fact, today is 2021-07-16. I create an event, and evolution uploads:
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
BEGIN:VEVENT
UID:c9ff63a992a009fe5cee754b1b4a8383143f221f
DTSTAMP:20210714T210548Z
LAST-MODIFIED:20210716T123839Z
CREATED:20210716T123839Z
...
END:VEVENT
END:VCALENDAR
so the DTSTAMP is not correct. The definition of DTSTAMP is https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.7.2:
Purpose: In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store.
The object was neither created, nor modified on 2021-07-14.