On Di, 2011-04-12 at 09:56 +0100, Stefan Vater wrote:
> Thanks Dinesh, that helped! I did not know how to connect syncevo to 
> akonadi...

Dinesh, Stefan, care to create a documentation page for this?
syncevolution.org has a Wiki.

> However, the synchronisation is a little bit strange. First, I 
> get the following messages when syncing:
> 
> me@mycomputer:~> syncevolution --sync slow nokia5230 addressbook
> [INFO] calendar+todo: inactive
> [INFO] calendar: inactive
> [INFO] todo: inactive
> [INFO] memo: inactive
> [INFO] Server sending SAN
> Local data changes to be applied remotely during synchronization:
> *** addressbook ***
> Comparison was impossible.
>
> [INFO] addressbook: started
> [INFO] addressbook: inactive
> 
> Synchronization successful.
> 
> Changes applied during synchronization:
> +---------------|-----------------------|-----------------------|-CON-+
> |               |         LOCAL         |        REMOTE         | FLI |
> |        Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
> +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
> |   addressbook |  0  |  0  |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> |   disabled, 0 KB sent by client, 43 KB received                     |
> |   120 item(s) matched                                               |
> |   item(s) in database backup: 120 before sync, 120 after it         |
> +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
> |        start Di 12 Apr 2011 10:44:22 CEST, duration 0:09min         |
> |               synchronization completed successfully                |
> +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
> 
> Data modified locally during synchronization:
> *** addressbook ***
> Comparison was impossible.
> 
> What does it mean "Comparison was impossible."?

Before starting a sync it means that no previous database dump for
"addressbook" was found: either there was no previous session, it did
not involve addressbook, or dumping failed.

Such a dump is normally created automatically, so after a sync there
should be one. It could be that the Akonadi source does not implement
this optional behavior. I'll check the source and report back...

> Furthermore, data is not changed 
> after modifications and a new sync. That might be related to the message 
> above...

No, that's unrelated. Changed where? On the phone or Akonadi?

> Another minor issue is that the picture of a contact is not 
> transfered...

Please run with increased loglevel=4 (just add that to the command
line), and then check in the log files in ~/.cache/syncevolution where
PHOTO data is lost resp. available.

> BTW, is there a possibility to see directly which items have been changed 
> how? Locally AND on the cell phone.

Locally the data comparison (once it works) will give you something like
that, in a format similar to diff. For remote changes only the
statistics above are available.

> Another comment concerning the help messages: When typing "syncevolution --
> sync ?" to get the different possibilities for sync modes, the descriptions 
> 
>      refresh-from-client = discard all remote items and replace with
>                            the items on the client
>      refresh-from-server = discard all local items and replace with
>                            the items on the server
> 
> are a little bit confusing for the case of synchronisation with a cell 
> phone. Here, client is the (remote) cell phone, and server is the (local) 
> PC. So roles have changed compared to the synchronisation with a network 
> server.

You are right. I always wanted to introduce more generic names, but
never had the time and also no good idea for the names:
refresh-from-peer is fairly straight-forward, but the other direction
isn't. refresh-the-peer/refresh-from-local?

-- 
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

Reply via email to