[SyncEvolution] Release preparations for 1.5.2

[Patrick Ohly]

On Wed, 2016-10-26 at 16:05 +0100, Graham Cobb wrote:
> > Any idea how to proceed with this? Is the policy-key workaround perhaps
> > not working as intended?
> 
> No, it is nothing to do with policy-key.  That gives different symptoms:
> either OK status but 0-length response or some 4nn status (419? I can't
> remember).
> 
> It looks like the problem is that a FolderSync is needed. You need to
> use --print-databases.  See the "Problems" in the Wiki page.

I'll try that, thanks for the hint... yes, it helped.

I'm now running into some new conversion issues for calendar data (time
zone related). To be checked.

> All my patch in bug 61869 does is enable --print-databases to be used as
> a manual workround for this problem. It doesn't attempt to solve it
> automatically.
> 
> If I remember correctly, one reason I didn't try to fix it automatically
> is that I couldn't reproduce the problem! If you can reproduce the
> problem reliably then maybe we can try to really fix it.

I didn't run into it with older Exchange or Google's ActiveSync
implementation, but now with Exchange 2016 I seem to hit it reliably.

> By the way, this raises a couple of interesting questions for your build
> testing. The EAS support (in the backend and in activesyncd) keeps state
> (in ~/.cache/activesync, in gsettings, and in the wallet). You might
> want to think about whether your automated testing wants to make sure it
> destroys all that state before running.

The automated testing already always starts from scratch.

-- 
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.