Michele Calgaro wrote:
On 2016/07/26 03:54 AM, deloptes wrote:
Slávek Banko wrote:
Dne ne 24. července 2016 deloptes napsal(a):
is it possible to use TDE 14.0.4 on debian unstable?
Builds directly for unstable (Sid) are not available. However, you can
try to use builds for Stretch.
I'm asking because I have in
# Trinity preliminary stable builds
stretch deps-r14 main-r14
So I was not sure if it is worth trying. I'll report back if it works.
I think it would be better to try building for sid instead of using the
stretch packages, sometimes sid and stretch have some major differences
for a while. Although given the highly volatile nature of sid I am not
sure whether it would be worth it or not. Stretch is definitely more
PS: yes, I am still around, just short of time :-)
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
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
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.