On Mi, 2011-09-07 at 00:03 -0400, Ross Vandegrift wrote:
On Tue, 2011-09-06 at 07:58 +0200, Tino Keitel wrote:
> ------- Original message -------
> > From: Ross Vandegrift <ross(a)kallisti.us>
> > To: syncevolution(a)syncevolution.org
> > Sent: 5.9.'11, 22:59
> > What's the best way to do this without messing up data or creating
> > duplicates? If I just take the synced phone and sync it with the
> > laptop, will that work?
> It should work. I did this once to test server operation. In my production
> setup, I use a dedicated syncevolution server that my desktop, laptop and
> phone use for syncing via HTTPS.
A bad thing: if you aren't familiar with syncevolution's quirky naming
scheme, you might think you should run "--sync refresh-from-server" on
the laptop. After all, the phone appears in the list of servers. This
of course deletes all of your data, since the phone is the client, even
if it is listed under "servers"...
Sorry for that. It's a known issue, but all that we could do in 1.2 was
to put it into the documentation:
**Warning:** in local sync, the sync config side acts as
server. Therefore the ``from-server`` variants
(``one-way-from-server``, ``refresh-from-server``) transfer data
from the sync config into the target config. The ``from-client``
variants transfer in the other direction, even if the target config
happens to access data on a remote server.
Hmm, it is not obvious that this also applies to syncing with devices
This issue came up before, but there was no conclusion about the naming.
Should it be "refresh/one-way-from-peer" and
"refresh-the-peer/one-way-to-peer"? "refresh/one-way-from-local" and
Good: this made me learn about the automatic syncevolution backups
how to restore. This works very well. I had no idea I had such good
After syncing with the laptop, going back to the desktop works, but
forces a slow sync. Repeating this seems to indicate that it always
needs to slow sync calendar+todo, even if there are no changes. Is this
No. Does this only happen for calendar+todo, but not for addressbook?
The syncevolution-log.html should contain some information about
"anchor" and "Alert" which explains why a slow sync is used. It's
hard to find, though. If you send me three logs (sync with computer A,
with B, with A again - please explain which one is which), then I can
have a look.
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.