Le samedi 29 septembre 2012 à 22:42 +0200, Patrick Ohly a écrit : > [...] > > > > 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
explain, not 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 Yes, definitely, it's the same calendar data so I didn't see any point in creating another account. > and local deviceId? Well I don't know what the deviceId depends on, but I thought that it would change with the newer HD installed. But maybe it hasn't been the case. > 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. > I find this reassuring. I'd bet that when I update my system "for real" --possibly doing a sync just before and just after-- everything will go well and I won't get this warning. So I think I should not bother you with this any more before trying the real update. Best regards, -- Daniel CLEMENT _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
