On Mi, 2013-11-20 at 11:23 +0100, tino.keitel+syncevolution(a)tikei.de wrote: It is an *excellent* idea to use the libsynthesis that matches the SyncEvolution release that you are packaging ;-) The reason is that this is what I have tested together. It may also contain API changes that SyncEvolution depends on or fixes for problems reported by SyncEvolution users. However, libsynthesis_3.4.0.47+syncevolution-1-3-99-6 has not been released yet. Consider the tag experimental until the actual tar archive gets published. In fact, the main reason why I haven't published 1.3.99.6 yet is a problem found during release testing which will require one more change in libsynthesis. I am working on it as we speak, eh, write. -- 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.

On Mi, 2013-11-20 at 13:29 +0100, tino.keitel+syncevolution(a)tikei.de wrote: Good catch. The version in configure is out-dated. I'll update that to match the latest upstream release, 3.4.0.47. -- 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.