[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-10-11 Thread Patrick Ohly
Patrick Ohly writes: > deloptes writes: > >> Hi Patrick, >> I am afraid I do not have your skills, but I am very thankful that you take >> your time to investigate. >> As mentioned before I always compile the old version from source (creating >> debian packages for the desktop and rpm for the

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-10-04 Thread Patrick Ohly
deloptes writes: > Hi Patrick, > I am afraid I do not have your skills, but I am very thankful that you take > your time to investigate. > As mentioned before I always compile the old version from source (creating > debian packages for the desktop and rpm for the phone) > , then compiling the

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-10-03 Thread deloptes
Hi Patrick, I am afraid I do not have your skills, but I am very thankful that you take your time to investigate. As mentioned before I always compile the old version from source (creating debian packages for the desktop and rpm for the phone) , then compiling the rest linked to the openobex

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-10-03 Thread Patrick Ohly
Patrick Ohly writes: > Patrick Ohly writes: > >> deloptes writes: >>> On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly wrote: >>> Emanoil Kotsev writes: > Hi, > It is the file UPGRADING.txt in openobex not the README > Upgrading to version 1.7Upgrading to version 1.6

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-09-03 Thread deloptes
Hi, for some reason I am not getting this on the mailing list. On Thu, Sep 3, 2020 at 12:45 PM Patrick Ohly wrote: > Patrick Ohly writes: > > > deloptes writes: > >> On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly > wrote: > >> > >>> Emanoil Kotsev writes: > >>> > Hi, > >>> > It is the file

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-09-03 Thread Patrick Ohly
Patrick Ohly writes: > deloptes writes: >> On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly wrote: >> >>> Emanoil Kotsev writes: >>> > Hi, >>> > It is the file UPGRADING.txt in openobex not the README >>> > Upgrading to version 1.7Upgrading to version 1.6 >>> >>> 1.7 is ancient (released 2016). I

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-08-05 Thread Patrick Ohly
deloptes writes: > On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly wrote: > >> Emanoil Kotsev writes: >> > Hi, >> > It is the file UPGRADING.txt in openobex not the README >> > Upgrading to version 1.7Upgrading to version 1.6 >> >> 1.7 is ancient (released 2016). I remember reading about "When

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-08-04 Thread deloptes
On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly wrote: > Emanoil Kotsev writes: > > Hi, > > It is the file UPGRADING.txt in openobex not the README > > Upgrading to version 1.7Upgrading to version 1.6 > > 1.7 is ancient (released 2016). I remember reading about "When using an > event loop that

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-08-03 Thread Patrick Ohly
Emanoil Kotsev writes: > Hi, > It is the file UPGRADING.txt in openobex not the README > Upgrading to version 1.7Upgrading to version 1.6 1.7 is ancient (released 2016). I remember reading about "When using an event loop that triggers on incoming data, you must call OBEX_HandleInput() after

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-31 Thread Emanoil Kotsev
Hi, It is the file UPGRADING.txt in openobex not the README Upgrading to version 1.7Upgrading to version 1.6 regards On Thursday, July 30, 2020, 1:08:31 AM GMT+2, Emanoil Kotsev wrote: Hi,strange I do not see this on the ML. I don't know how to debug this. The problem is that openobex

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-29 Thread Emanoil Kotsev
Hi,strange I do not see this on the ML. I don't know how to debug this. The problem is that openobex changed - if you look in the README it says what needs to be done to upgrade from 1.5 to 1.7.I did not have time and ability to go deeper into openobex. The problem is that  after SAN is sent it

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-25 Thread Patrick Ohly
Graham Cobb writes: > On 24/07/2020 20:38, Patrick Ohly wrote: > * At the top of that list is ActiveSync support. activesyncd no longer >> builds on Debian Stretch because it depends on libgnome-keyring, which >> was removed. It probably can be ported to libsecret, but that's >> extra work.

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-25 Thread Patrick Ohly
deloptes writes: > Hi Patrick, > glad to hear such good news from you - really appreciate your work. > I am actively using SyncEvolution on Debian Buster with TDE and with > Sailfish OS phone. > > I was wondering about openobex-1.7 (aka libopenobex2) - is it possible to > get it working with it?

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-24 Thread Graham Cobb
On 24/07/2020 20:38, Patrick Ohly wrote: > [Most of the text below was written in December 2019, but than > unintentionally sent to an internal mailing list - no surprise that I > never got any response!] > > Hello! > > Over the Christmas holidays I worked on building a new SyncEvolution

[SyncEvolution] Re: new SyncEvolution binaries, dropping features?

2020-07-24 Thread deloptes
Hi Patrick, glad to hear such good news from you - really appreciate your work. I am actively using SyncEvolution on Debian Buster with TDE and with Sailfish OS phone. I was wondering about openobex-1.7 (aka libopenobex2) - is it possible to get it working with it? It seems to be the new default