Open Ian2020 opened 8 months ago
Hopefully if vdirsyncer could just sort the timezones or something these differences could be ignored/auto-resolved. Thanks for any help!
I intend to write a separate tool which can resolve conflicts between semantically equivalent icalendar
entries.
That will be usable as a command for conflict resolution.
I'm also getting the same thing with orage / gmail syncing, such a tool would be brilliant.
Hi,
I mentioned this on IRC chat and it was suggested I raise an issue. I've got a local ics file (type=singlefile) that recently starting conflicting against the server (type=caldav) for every item. It looks like my calendar app (Evolution/GNOME) changed the order (but not the content) of all the VTIMEZONE entries in the .ics file.
I've never seen this before in many years of using vdirsyncer and Evolution. My guess is a recent change in how Evolution orders timezones when it writes to file probably triggered the conflicts for vdirsyncer.
vdirsyncer version: 0.18.0
Config:
The .ics file used to start like this when there were no conflicts (just showing the first timezone entry):
Then it changed to start like this and now every item causes a conflict in vdircyncer:
I tried manual conflict resolution with a diffing tool and I could see that if I rearranged the VTIMEZONE components I could get the files to match exactly. So all that has changed in my .ics file is the ordering I believe.
Hopefully if vdirsyncer could just sort the timezones or something these differences could be ignored/auto-resolved. Thanks for any help!