Hi Graham,
it took me a while to get the basics working.
Regarding the configuration this is what I did for testing TDEPIM to LOCAL file
store
syncevolution --configure \
--template none \
username= \
password= \
addressbook/backend=tdepim-contacts \
addressbook/database="kxXrRFzP9c" \
addressbook/databaseFormat="text/vcard" \
calendar/backend=tdepim-calendar \
calendar/database="ZsPZokpoTg" \
calendar/databaseFormat="text/calendar" \
todo/backend=tdepim-tasks \
todo/database="ZsPZokpoTg" \
todo/databaseFormat="text/calendar" \
memo/backend=tdepim-memos \
memo/database="ZsPZokpoTg" \
memo/databaseFormat="text/plain" \
target-config@${peer} addressbook calendar todo memo
# Remove the "--source-property type" lines to use the Evolution backends.
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://target-config@${peer} \
peerIsClient=1 \
--source-property type=file:text/vcard:3.0 \
--source-property evolutionsource=file://${datapath}/addressbook \
${peer} addressbook
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://target-config@${peer} \
peerIsClient=1 \
--source-property type=file:text/calendar:2.0 \
--source-property evolutionsource=file://${datapath}/calendar \
${peer} calendar
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://target-config@${peer} \
peerIsClient=1 \
--source-property type=file:text/calendar:2.0 \
--source-property evolutionsource=file://${datapath}/todo \
${peer} todo
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://target-config@${peer} \
peerIsClient=1 \
--source-property type=file:text/plain:1.0 \
--source-property evolutionsource=file://${datapath}/memo \
${peer} memo
I had to change something in the LocalTransportAgent.cpp to get the peer
exiting and sync completing
My addressbook works fine. Calendar/todo/memo is missing the data at the end.I
need to have a look why now.
regards
On Saturday, February 6, 2016 1:26 PM, Graham Cobb
<[email protected]> wrote:
On 06/02/16 09:56, deloptes wrote:
> It does now exit, but staying there after
>
> Synchronization successfull
> Changes applied ....
> Data modified ....
> *** @..../addressbook ***
> no changes
I assume you meant "It does NOT exit". In my experience, the appearance
of syncevolution not exiting is often due to the "changes" perl script
which, in may case, can take a VERY long time. I don't remember the
name of the script offhand but while it is "hung" you may want to see if
there is a process running perl on your system.
I recommend that while initially testing you set "printChanges=0" (if
you have a lot of data you may want to set dumpData=0 as well, except
when you really want to save the data). Turning off both those at least
means you are really just testing the sync code.
That may not be your problem at all, but it is worth checking.
Graham
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
