On Mi, 2011-01-05 at 00:30 +0000, Irihapeti wrote: > I created a test recurring event on the phone. After syncing to > Evolution, the event shows up as it should, BUT it also appears on the > following day as well. Times are correct on both dates. > > I can edit it in Evolution to remove the extra occurrences, resync, and > everything is fine. I can edit other stuff on the phone, such as turn > the alarm off, but if I subsequently try to change the date of the event > on the phone, the problem recurs. > > The output from the phone, using syncml-ds-tool, shows: > > -----BEGIN CHANGE----- > BEGIN:VCALENDAR > VERSION:1.0 > TZ:+12 > DAYLIGHT:TRUE;+13;20100925T140000Z;20110402T130000Z;; > DAYLIGHT:TRUE;+13;20110924T140000Z;20120331T130000Z;; > BEGIN:VEVENT > UID:o7D5s1844F0Ke432gA7Le1 > SUMMARY:New > DTSTART:20110205T200000Z > DTEND:20110205T210000Z > CLASS:PUBLIC > RRULE:W1 SU 20110220T090000 > LAST-MODIFIED:20110105T001640Z > PRIORITY:5 > END:VEVENT > END:VCALENDAR > -----END CHANGE----- > > SyncEvolution shows: > > before sync | after sync > removed during sync < > > added during sync > ------------------------------------------------------------------------------- > BEGIN:VCALENDAR BEGIN:VCALENDAR > VERSION:2.0 VERSION:2.0 > BEGIN:VEVENT BEGIN:VEVENT > > SUMMARY:New > > DTEND:20110205T210000Z > > DTSTART:20110205T200000Z > > PRIORITY:5 > > RRULE:BYDAY=SA,SU;FREQ=WEEKLY;UNTIL > > =20110220T090000 > > SEQUENCE:0 > > UID:o7D5s1844F0Ke432gA7Le1 > > END:VEVENT > > END:VCALENDAR > -------------------------------------------------------------------------------
What is the expected end day of this recurring event? What is your time zone? Do both phone and your desktop system use the same zone? The definition of the time in UNTIL 20110220T090000 is unfortunately a bit vague. Perhaps it needs to be adapted in the vCalendar 1.0 -> iCalendar 2.0 conversion. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
