Le vendredi 29 mai 2015 à 17:04 +0200, Patrick Ohly a écrit : > On Fri, 2015-05-29 at 16:44 +0200, Daniel CLEMENT wrote: > > daniel@e6330d ~ $ syncevolution --sync refresh-from-remote memotoo memos > > syncevolution: error while loading shared libraries: libical.so.0: > > cannot open shared object file: No such file or directory > > Which version of SyncEvolution is that?
It's syncevolution-evolution 1:1.5-1 syncevolution-bundle 1:1.5-2 but while the main (older) PC (the one I'm writing from) uses http://downloads.syncevolution.org/apt/ (stable main) the 2nd one (upgraded, which has problems) is set to https://download.01.org/syncevolution/apt/ (stable main)... > > 1.5 does not link against libical.so.0 (ldd `which syncevolution ` | > grep libical). ... and the result of this command line gives different results: (old PC) no output, which I assume is normal; (upgraded PC) daniel@e6330d ~ $ ldd `which syncevolution ` | grep libical libical.so.0 => /usr/lib/libical.so.0 (0x00007f680aa6b000) libicalss.so.0 => /usr/lib/libicalss.so.0 (0x00007f680a852000) libicalvcal.so.0 => /usr/lib/libicalvcal.so.0 (0x00007f680a63c000) and indeed if the result of syncevolution --version begins with SyncEvolution 1.5 it continues slightly differently: (old PC) using libedataserver-1.2.so.16 using libecal-1.2.so.11 using libecal-1.2.so.11 using libbluetooth.so.3 (upgraded PC) using libical.so.1 using libical.so.1 using libbluetooth.so.3 So this gives me the idea to set the Syncevolution repository to http://downloads.syncevolution.org/apt/ on the new PC and reinstall both syncevolution packages from there. > > However, Debian renamed libical1 into libical1a, and while I have > adapted the package of SyncEvolution to accomodate for that, that change > is not released yet. So your observation is right, currently > SyncEvolution pulls in libical0. > -- Daniel CLEMENT _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
