On Mo, 2011-07-11 at 14:04 +0200, Ove Kåven wrote: > Den 11. juli 2011 08:34, skrev Patrick Ohly: > > On Fr, 2011-07-01 at 21:27 +0200, Ove Kåven wrote: > >> Den 01. juli 2011 16:12, skrev Patrick Ohly: > >>> Trying again with a recent commit like 62239e5c9 would be worthwhile. > >> > >> Hmm. I think that works (so far). > > > > A random thought struck me yesterday: the slow sync matching of calendar > > items is based on the assumption that CalDAV server and local backend > > support UIDs. This won't work with the Maemo 5 backend. You'll need to > > stick with the traditional approach of comparing properties. > > Well, it still supports LUIDs. I thought a UID<->LUID database would > probably be enough?
That mapping is lost when doing a slow sync. In that case all that is available to SyncEvolution is the local data (which no longer has the UID) and the CalDAV server data (which has it). The slow sync needs to re-establish the UID<->LUID mapping. > > I don't have a configuration mechanism in place for this yet. In the > > meantime, can you perhaps patch SyncContext.cpp and comment out the > > following code on Maemo 5? > > "Patch and comment out"... is the patch to comment this out, or did you > mean something else by "patch"? The patch would be to comment this out. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
