On Thu, 2011-09-08 at 09:17 +0200, Patrick Ohly wrote:
On Mi, 2011-09-07 at 17:48 -0400, Ross Vandegrift wrote:
Let me phrase the question differently: if the options for "--sync" aka
"--source-property sync" had been named as follows, would that have
avoided the problem?
$ syncevolution --sync ?
Requests a certain synchronization mode when initiating a sync:
two-way = only send/receive changes since last sync
slow = exchange all items
refresh-from-remote = discard all local items and replace with
the items on the peer
refresh-from-local = discard all items on the peer and replace
with the local items
one-way-from-remote = transmit changes from peer
one-way-from-local = transmit local changes
disabled (or none) = synchronization disabled
refresh/one-way-from-server/client are also supported. Their use is
discouraged because the direction of the data transfer depends
on the role of the local side (can be server or client), which is
not always obvious.
When accepting a sync session in a SyncML server (HTTP server), only
sources with sync != disabled are made available to the client,
which chooses the final sync mode based on its own configuration.
When accepting a sync session in a SyncML client (local sync with
the server contacting SyncEvolution on a device), the sync mode
specified in the client is typically overridden by the server.
Yes, this explains the situation quite clearly - I think this is a clear
> And even if that doc snippet doesn't clearly refer to
bluetooth, I still
> didn't read it...
I know, this warning isn't the right way of solving the problem. From
which documentation did you learn about the available sync modes?
I looked at the manpage.
To me this looks like the phone doesn't properly distinguish
peers it syncs with. That pretty much breaks the sync topology where the
phone is the hub through which all data must pass.
Aha - that's very helpful. This makes some sense, it's a Symbian S40
phone. Seems likely that they'd make some (bad) simplifying
Perhaps you can make your desktop that hub instead by synchronizing
the laptop and the phone against it? USB Bluetooth dongles are cheap. Or
make the laptop the hub, synchronizing against the phone via Bluetooth
and against the desktop via HTTP
Yea, something like this should help me a lot. I can keep the two
computers in sync so the phone doesn't need to distinguish between them.
I'll try this next time I get the chance. Thanks very much Patrick -
this was really helpful.
Ross Vandegrift <ross(a)kallisti.us>