On Sat, 2012-09-29 at 18:39 +0200, Daniel CLEMENT wrote:
Thanks for your help!
Le vendredi 28 septembre 2012 à 16:13 +0200, Patrick Ohly a écrit :
> On Fri, 2012-09-28 at 15:39 +0200, Daniel CLEMENT wrote:
> > [...] When I launched the new Syncevolution, it complained about a
> > problem during the last sync -- it was not the case!
> What was the exact problem? Did you use the UI or command line?
Well maybe it wasn't a real problem. I'm trying to attach a screenshot,
but I don't know if it can reach the list. The message says "a problem
has occurred during the last sync. A normal sync is now impossible. The
server suggests a slow sync..." etc.
This sounds like an unexpected slow sync, as you said.
> Getting a copy of your ~/.cache/syncevolution directory would be
> with information about which session in it was the one that showed the
> error described above.
I made a copy of this directory, but it's fairly large: is there any
particular file which would be more helpful?
I was looking for the status.ini and syncevolution-log.html files,
because they often contain more detailed error messages than what the UI
shows. But don't bother, I think I know what it is - see below.
> > So I did not do the slow sync that was offered, and stopped
> > restarting my main system, the syncing resumed flawlessly.
> > So, is there any steps I should take before updating? Should I go ahead
> > with the slow sync, or rather not transfer the Syncevolution settings
> > and re-create them from scratch?
> It should be fine to just upgrade.
Sure. To be clearer: the "draft" system I used to test the updates is
just my former HD which I booted from. So it hadn't been running
Syncevolution for a while.
Can't we explaine my problem just by this lag between the Funambol
server and the (old) status of the Syncevolution files on the old HD?
Perhaps when I update the "real" system, which syncs several times a
day, everything will be fine...
Does the draft system and the real system use the same Funambol login
and local deviceId? If yes, then that explains the unexpected slow sync.
The Funambol server cannot tell your old and new system apart. It does
change tracking per deviceId. When the old system connects again, change
tracking information (in particular the "anchors") don't much, and thus
a slow sync becomes necessary.
Not allowing the slow sync was the right decision, because otherwise the
new system would have run into the same problem and been forced to also
do a slow sync.
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.