4:42 a.m.
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
useful,
> 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
there. When
> > 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.
8:34 p.m.
New subject: [SyncEvolution] Recent updates under Linux Mint Debian + unexpected slow sync
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
4:06 a.m.
New subject: [SyncEvolution] Recent updates under Linux Mint Debian + unexpected slow sync
On Sun, 2012-09-30 at 14:34 +0200, Daniel CLEMENT wrote:
Le samedi 29 septembre 2012 à 22:42 +0200, Patrick Ohly a écrit :
> 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,
It's set in the sync config when the config is created for the first
time. Therefore one should not simply copy the .config directory to
configure a second computer that'll be used simultaneously; one has to
adapt the device ID on the copy. The recommended approach is to create a
new config from scratch.
but I thought that it
would change with the newer HD installed. But maybe it hasn't been the
case.
No, changing hardware does not affect the device ID. Otherwise it would
not be possible to move an OS installation or HOME directory from one
computer to the next and continue seamlessly.
The caveat is that moving back and forth between old and new system is
not possible.
--
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.
3040
days inactive
3041
days old
syncevolution@synevolution.org
2 comments
2 participants
participants (2)
-
Daniel CLEMENT -
Patrick Ohly