Hello!
Kyros follow-up emails didn't make it to the list, and I missed the
personal email in my email backlog until after the holidays. From a
SyncEvolution command line invocation:
=====================================================
~ $ syncevolution funambol
[INFO] todo: starting first time sync, two-way
[INFO] memo: starting first time sync, two-way
[INFO] addressbook: starting first time sync, two-way
[INFO] calendar: starting first time sync, two-way
[INFO] memo: first time sync done unsuccessfully
[ERROR] memo: unexpected slow sync (local, status 22000)
[INFO] addressbook: first time sync done unsuccessfully
[ERROR] addressbook: unexpected slow sync (local, status 22000)
[INFO] calendar: first time sync done unsuccessfully
[ERROR] calendar: unexpected slow sync (local, status 22000)
[ERROR] Aborting because of unexpected slow sync for source(s): addressbook
calendar memo
[INFO] Doing a slow synchronization may lead to duplicated items or
lost data when the server merges items incorrectly. Choosing
a different synchronization mode may be the better alternative.
Restart synchronization of affected source(s) with one of the
following sync modes to recover from this problem:
slow, refresh-from-server, refresh-from-client
Analyzing the current state:
syncevolution --status funambol addressbook calendar memo
Running with one of the three modes:
syncevolution --sync [slow|refresh-from-server|refresh-from-client]
funambol addressbook calendar memo
[INFO] todo: first time sync done unsuccessfully
[ERROR] todo: aborted on behalf of user (local, status 20017)
======================================================
Kyros, picking any of the sync modes given in the example command line
above would get you back into the normal state where syncing is
incremental. Which mode is preferred depends on your situation, and the
software cannot decide for you. Is there anything that can be changed in
the INFO message to explain the situation better?
Alternatively you can also disable slow sync detection, which has the
same effect as automatically doing a slow sync:
syncevolution --configure --sync-property preventSlowSync=0 funambol
In the context of Maemo and its UI, it probably would be better to
disable slow sync detection for all configs, because most users will
never see this explanation and the UI doesn't have the kind of "recovery
dialog" that the GTK sync-ui offers for handling this case (right?).
Ove, what do you think?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
