[Syncevolution-issues] [MeeGo Projects - Bug 10265] Sync must be executed twice to really transfer calendar events
http://bugs.meego.com/show_bug.cgi?id=10265
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick.ohly(a)intel.com
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2010-11-21 05:37:21 PST ---
(In reply to comment #0)
BUG DETAILED DESCRIPTIONS
===========================================================
I'm using syncevolution to keep my caldav calendar and my Nokia N900 calendar
in sync. On the PC (caldav) I've got syncevolution 1.1 running as http server,
whereas on the Nokia I have syncevolution 1.0 (no more recent image available)
running as http client.
How does SyncEvolution access the calendar data in your CalDAV server?
(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.
(In reply to comment #5)
Created an attachment (id=3581)
-->
(http://bugs.meego.com/attachment.cgi?id=3581) [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?
--
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.