http://bugs.meego.com/show_bug.cgi?id=10265

--- Comment #8 from alainlux <[email protected]> 2010-11-21 08:45:27 PST ---
(In reply to comment #6)
> How does SyncEvolution access the calendar data in your CalDAV server?

See attached .config/syncevolution/default/sources/calendar/config.ini

> 
> (In reply to comment #3)
> > The weird thing is that when sync runs the second time, it wipes the
> > ~/.cache/syncevolution directory of the first run. However, the next run 
> > (after
> > another change) will not wipe the directory of the second run.  
> 
> This is probably the "smart" eviction policy for old session directories what
> you see here. It tries to keep the number of session directories below the
> configured number by deleting sessions in which nothing happened (no changes,
> no errors) first. You can turn this off by setting maxlogdirs=0.

Good, makes sense

> 
> (In reply to comment #5)
> > Created an attachment (id=3581)
 --> (http://bugs.meego.com/attachment.cgi?id=3581) [details] [details]
> > stdout of syncevo-dbus-server on server (PC), first run
> > 
> > This is interesting. Near the end, it shows that it did already pick up the
> > change... also, in the summary, it noticed that the number of items went 
> > from
> > 158 to 159... but still didn't do any modifications, neither locally, nor
> > remotely...
> 
> Hmm, this output says that one item was created on the PC. Is that the item
> that you created manually in order to sync it to the N900?  

Yes, that was the item that I created on the PC in order to sync it to the
N900. So it did pick it up, but didn't mention its existence to the N900...

-- 
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to