On 26/10/16 17:10, Patrick Ohly wrote:
I'll try that, thanks for the hint... yes, it helped.
I'm now running into some new conversion issues for calendar data
zone related). To be checked.
I can't say I am surprised. The time zone stuff is fairly fragile -- I
seem to remember putting in some hacks to try to make the best of a bad
job. Make sure that the timezone of the syncevolution system is the
same as the timezone of the Outlook calendar that creates the events (I
seem to remember there are some cases where I had to make that
assumption, which is most likely true for most people).
I have not seen any problems with Exchange syncs, although I am getting
problems when I sync Exchange<->Files<->Owncloud. I think they are to do
with handling exceptions in repeated events (the failing items are to do
with repeating weekly meetings which I have been moving around in
Outlook). But I am not sure if the real problem is creating bad files
from the Exchange events or syncing the files with Owncloud.
I have run out of time to look into it further before I go on holiday,
unfortunately. But I really don't know if this is a regression -- my
regular syncs had stopped working for some time (due to changes in our
Exchange setup) and I (stupidly) didn't get them working again until
after I had installed the 1.5.2 code. My suspicion is that it isn't a
regression as there have been no changes in those areas (and the
repeating event support is even more flakey than timezone support :-( ).