On Fri, 2015-05-29 at 17:56 +0200, Daniel CLEMENT wrote: > 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)
I'm very suspicious about the binary that you are running on this upgraded PC. Please check that it really comes from the official .deb: which syncevolution file `which syncevolution` md5sum `which syncevolution` dpkg -S `which syncevolution` Assuming that you are on amd64 (aka 64 bit), that should give: $ which syncevolution /usr/bin/syncevolution $ file `which syncevolution` /usr/bin/syncevolution: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.15, BuildID[sha1]=05708d05d234df537c464157b331ddb901d52600, not stripped $ md5sum `which syncevolution` c0405aa56a9976159386c54b7ac47ae1 /usr/bin/syncevolution $ dpkg -S `which syncevolution` syncevolution-bundle: /usr/bin/syncevolution -- 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
