From patrick.ohly at intel.com Mon Aug 3 14:16:35 2020 From: patrick.ohly at intel.com (Patrick Ohly) Date: Mon, 3 Aug 2020 16:16:35 +0200 Subject: [SyncEvolution] Re: new SyncEvolution binaries, dropping features? In-Reply-To: <1999128678.6936493.1596177452997@mail.yahoo.com> References: <865359074.6474507.1596064111409@mail.yahoo.com> <1999128678.6936493.1596177452997@mail.yahoo.com> Message-ID: 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 each call to OBEX_Request() to actually send the request" (https://gitlab.com/openobex/mainline/-/blob/master/UPGRADING.txt). If I remember correctly, my conclusion was that SyncEvolution does that, but I am not sure anymore. > 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 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) hangs waiting for PUT or whatever and does not move forward. > > I tried few weeks ago building bueto-syncml for the (now) Sailfish OS > with openobex 1.7 and I had syncevolution 1.5.3 with openobex 1.5 on > the PC, but it hangs on the phone the same way it hangs on the PC if > it is build against openobex 1.7. I couldn't find out, how I can get > log from the plugin there as it is started in a thread an nothing > logs. Can you ensure that you have working setup and then just update the SyncEvolution side to openobex 1.7? Does that then start to fail? It's not clear to me from the description above whether that is something that you have tested. -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From deloptes at gmail.com Tue Aug 4 19:49:23 2020 From: deloptes at gmail.com (deloptes) Date: Tue, 4 Aug 2020 21:49:23 +0200 Subject: [SyncEvolution] Re: new SyncEvolution binaries, dropping features? In-Reply-To: References: <865359074.6474507.1596064111409@mail.yahoo.com> <1999128678.6936493.1596177452997@mail.yahoo.com> Message-ID: 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 triggers on incoming data, you must call > OBEX_HandleInput() after each call to OBEX_Request() to actually send > the request" > (https://gitlab.com/openobex/mainline/-/blob/master/UPGRADING.txt). > If I remember correctly, my conclusion was that SyncEvolution does that, > but I am not sure anymore. > > I am also not sure where and how this has to be done. I think I have looked into SyncEvolution few years ago and it seemed to call OBEX_HandleInput(), but I am not quite sure at all. It could be also something completely different. > > regards > > On Thursday, July 30, 2020, 1:08:31 AM GMT+2, Emanoil Kotsev < > deloptes at yahoo.com> wrote: > > > > 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) hangs waiting > for PUT or whatever and does not move forward. > > > > I tried few weeks ago building bueto-syncml for the (now) Sailfish OS > > with openobex 1.7 and I had syncevolution 1.5.3 with openobex 1.5 on > > the PC, but it hangs on the phone the same way it hangs on the PC if > > it is build against openobex 1.7. I couldn't find out, how I can get > > log from the plugin there as it is started in a thread an nothing > > logs. > > Can you ensure that you have working setup and then just update the > SyncEvolution side to openobex 1.7? Does that then start to fail? It's > not clear to me from the description above whether that is something > that you have tested. > > Yes I did exactly this - installed openobex2 (1.7) with dev package from debian, compailed SyncEvolution 1.5.2 or 1.5.3 against it and then it does not work any more. Then removed openobex2 and installed openobex1 with dev package, compailed SyncEvolution 1.5.2 or 1.5.3 against it and then it works again. Same experience with buteo-syncml. Buteo-syncml with openobex1 works and with openobex2 does not work. I wrote once to the maintainer of openobex, but he was sparse to answer that it means the steps to upgrade from 1.5 to 1.7 were not followed and send me back to the UPGRADE file. In theory it should be possible that one end is using openobex-1.5 and the other 1.7 - the protocol is the same, so I do change only openobex on one end at a time. I don't know if I change on both ends it would start working. Do you think it is worth trying? Thank you and regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick.ohly at intel.com Wed Aug 5 09:10:10 2020 From: patrick.ohly at intel.com (Patrick Ohly) Date: Wed, 5 Aug 2020 11:10:10 +0200 Subject: [SyncEvolution] Re: new SyncEvolution binaries, dropping features? In-Reply-To: References: <865359074.6474507.1596064111409@mail.yahoo.com> <1999128678.6936493.1596177452997@mail.yahoo.com> Message-ID: 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 using an >> event loop that triggers on incoming data, you must call >> OBEX_HandleInput() after each call to OBEX_Request() to actually send >> the request" >> (https://gitlab.com/openobex/mainline/-/blob/master/UPGRADING.txt). >> If I remember correctly, my conclusion was that SyncEvolution does that, >> but I am not sure anymore. >> >> > I am also not sure where and how this has to be done. I think I have looked > into SyncEvolution few years ago and it seemed to call OBEX_HandleInput(), > but I am not quite sure at all. It could be also something completely > different. Perhaps calling OBEX_HandleInput unconditionally after OBEX_Request is really missing. I don't know exactly whether it now gets called only when the fd is ready. > In theory it should be possible that one end is using openobex-1.5 and the > other 1.7 - the protocol is the same, so I do change only openobex on one > end at a time. I don't know if I change on both ends it would start > working. Do you think it is worth trying? No, changing only one side is the right approach. I also doubt that updating both sides will magically solve it - that would imply that openobex is no longer compatible with other OBEX implementations. -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From xy at roth.biz Thu Aug 20 12:29:48 2020 From: xy at roth.biz (Roth) Date: Thu, 20 Aug 2020 14:29:48 +0200 Subject: syncevolution funambol: Not working after upgrade to newest Debian Testing Version In-Reply-To: References: <6bf8bf9d5c085966f1fde0abc7a2d86e3bd056ec.camel@roth.biz> Message-ID: <224a9e8b753dccbf9f514ad42e195d7e1cc20c87.camel@roth.biz> Hello Patrick, any news on this issue. I stll can't synchronize. I'm getting the same error. Kind regards Christian On Tue, 2019-12-03 at 09:37 +0100, Patrick Ohly wrote: > Roth writes: > > Hello Patrick, > > I can't syncronize any more. After 7 years of successful sync > > viaFunambol server, it is not working. > > This is the error: > > First ERROR encountered: error code from SyncEvolution error > > parsingconfig file (local, status 20010): calmobile: backend not > > supported byany of the backend modules (syncxmlrpc, > > synctdepimnotes, synctdepimcal,synctdepimabc, syncsqlite, > > syncqtcontacts, syncpbap, syncmaemocal,synckcalextended, syncfile, > > syncdav, provideroauth2, providergoa,platformtde, platformkde, > > platformgnome) or not correctly configured(backend=calendar > > databaseFormat= syncFormat=text/calendar > > Which SyncEvolution binaries are you using? > The ones from syncevolution.org don't work on Debian testing > becauseEvolution Data Store (EDS) changed its API. I need to update > them and doa new release which Tino then hopefully can get into > Debian again. Itwas removed because of the Python2 dependency. -------------- next part -------------- An HTML attachment was scrubbed... URL: