Slávek Banko wrote: Thanks, I'm asking because I have in cat /etc/debian_version stretch/sid and in cat /etc/apt/sources.list deb http://ftp.at.debian.org/debian/ sid main deb-src http://ftp.at.debian.org/debian/ sid main # Trinity preliminary stable builds deb http://mirror.xcer.cz/trinity-sb stretch deps-r14 main-r14 So I was not sure if it is worth trying. I'll report back if it works. regards

Michele Calgaro wrote: Strange but I got notification in both my mail boxes (yahoo and gmail) regarding this thread. I'm sorry I did not write back here. I was pretty busy and did not hear anything from syncevolution team. I don't think packages are yet available in the stretch branch, so I still do not know what is best to do. IMO we have two options and one way to go. 1. short term I could upload the source code for the TDE backend somewhere and anyone could download and add it to the syncevolution tree and build custom installation (it is not possible to build debian packages). 2. prepare patch package based sources that are already uploaded on debian sid. This means use the src from debian and apply a patch on top to get debian packages for sid. Whenever syncevo src packages are uploaded to stretch we could apply 2. to these srcs All this means that buildind of trinity desktop packages of syncevolution will stay with us. I'll need some help to get the proper routines setup. I still have some issues partially with mangled chars in contacts/todos and notes. I think the best approach would be to reactivate the testing (as I did for the address book), reproduce, debug and fix whatever is causing the problems. However I did not hear anything from Fat Zer who mentioned he could setup the build system to support testing and have unified way to use the already testing code. I could easily move from automake to cmake after the experience with the abc and cal part. Let me know what you think. Thanks