On 1/21/10 2:26 AM, Benjamin Scherrer wrote: > Hi, > > this bug seems to be still active to me. I'm up to date on Debian > testing amd64 with the versions: > > ardour 2.8.4-3 > librdf0 1.0.10-1 > librdf0-dev 1.0.10-1 > librasqal2 0.9.17-1 > librasqal2-dev 0.9.17-1 > > But I still get this console output: > > $ /usr/bin/ardour2 > /usr/lib/ardour2/ardour-2.8.4: error while loading shared libraries: > librasqal.so.1: cannot open shared object file: No such file or directory > > Even if I build Ardour from source, I get: > $ /usr/local/bin/ardour2 > /usr/local/lib64/ardour2/ardour-2.8.4: error while loading shared > libraries: librasqal.so.1: cannot open shared object file: No such file > or directory
librasqal.so.1 has not been packaged for some years librasqal.so.2 was introduced in rasqal 0.9.17-1 of 16 Dec 2009 and is the one in stable. (librasqal.so.3 just arrived in 0.9.24-1 of 31 Jan 2011 and is in sid but not testing yet) So the ardour2 binary you have there has broken dependencies or was compiled against the wrong library or something else. An aside at Ardour: If I look in sid at ardour, it says: Build-Depend: ... libraptor1 (>= 1.4.19), librasqal2 (>= 0.9.18), librdf0 (>= 1.0.9), which is shortly going to break since the latest librdf0 will shortly require librasqal3 and libraptor2. If ardour really uses raptor V1 API/ABI, it'll need porting. If it uses librdf API/ABI, it just needs a rebuild. It's surprising it requires both dependencies; does it really uses those symbols? Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
