On Thu, 2015-05-28 at 16:01 +0200, Daniel CLEMENT wrote: > Le jeudi 28 mai 2015 à 12:36 +0200, Patrick Ohly a écrit : > > [...]That's not what I meant. When you run > > "ldd /usr/lib/syncevolution/backends/syncecal-3.so | grep ecal" it will > > point you to a libecal version that belongs to an obsolete EDS. > > > > Check in aptitude under "obsolete" packages, or use "dpkg -S" to locate > > the owner of that libecal*.so*. Get rid of those. > > It pointed me to libecal-1.2-15, which was from the old (3.8) version. I > guess it was not removed by the upgrade because the new (3.12) has a > different name (libecal-1.2-16). > > > > Same for all other obsolete /usr/lib/libe*.*so* files. > > > I checked carefully and I had to suppress 4 more: > libedata-cal-1.2-20 > libebackend-1.2-6 > libedatabook-1.2-17 > libedataserver-1.2-17 > for which the newer version also has a different name.
What about libical? > I confirmed with a search for version in Synaptic that all my > Evolution-related packages are from the 3.12 now. > > But I still cant sync. Can you create and later read memos via the Evolution UI? Can you do the --print-items of those with the SyncEvolution command line? There's no point trying to sync if that already fails. Can you check whether your memo storage is really the local storage? In other words, your .config/evolution/sources/ file with "Memo List" inside should have BackendName=local. -- 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
