Re: [SyncEvolution] TDEPIM sync questions

2016-02-10 Thread deloptes
Patrick Ohly wrote: > Another test might be to set up syncing between file backends. For that > replace the TDE datastores on the target side of your sync config with > another file backend, like you did on the local side. If that also > fails, then it should be a problem that is completely

Re: [SyncEvolution] TDEPIM sync questions

2016-02-09 Thread deloptes
Patrick Ohly wrote: > LocalTransportAgent::storeSyncReport() is the parent side and logs "got > child sync report" once the data made it across the local D-Bus > connection. Do you see that when running with SYNCEVOLUTION_DEBUG and > loglevel=10? yes I see status=200 - everything went good, but

Re: [SyncEvolution] TDEPIM sync questions

2016-02-08 Thread deloptes
Patrick Ohly wrote: > In case of a local sync, two processes are involved. You need to attach > to syncevo-local-sync (gdb -p `pidof syncevo-local-sync`) and have a > look where that one is stuck when the problem occurs. Thanks again for the hint. I do not have that much experience in debugging

Re: [SyncEvolution] TDEPIM sync questions

2016-02-07 Thread deloptes
deloptes wrote: > > I think I have a problem with understanding the configuration and how I > can create a test setup where I have a local sync server (file backend) > and TDE PIM on the other side. > It looks like it worked for addressbook, but trying to reproduce or extend >

Re: [SyncEvolution] TDEPIM sync questions

2016-02-05 Thread deloptes
Thanks for all the information. Patrick Ohly wrote: > That confirms my theory: I bet your register_func object linked into > both shared modules, and then each module registers both kinds of data. > > You need two registration files, one per module, and only register data > provided by that

Re: [SyncEvolution] TDEPIM sync questions [solved double register]

2016-02-05 Thread deloptes
Patrick Ohly wrote: > That confirms my theory: I bet your register_func object linked into > both shared modules, and then each module registers both kinds of data. > > You need two registration files, one per module, and only register data > provided by that module in the file. I solved this -

Re: [SyncEvolution] TDEPIM sync questions

2016-02-05 Thread deloptes
Patrick Ohly wrote: > On Wed, 2016-02-03 at 20:05 +0100, deloptes wrote: >> Hi to all @syncevolution, sorry for bothering you, but I hope one could >> save me some digging by answering my questions. >> I thank you in advance for the patience and support. >> >>

<    1   2