On Fri, 2010-07-16 at 16:40 +0200, Matt N wrote: > shotwell: error while loading shared libraries: libexiv2.so.6: cannot > open shared object file: No such file or directory > > The packaging says shotwell requires libexiv2-9 which is now in > unstable instead of 2-6, I get this error whenever I try to run > shotwell. I don't really know packaging, but is it possible it just > got compiled against the old version of libevix2?
The build log for the i386 binNMU shows that both libexiv2-6 and libexiv2-9 were installed during the build. This appears to be a side-effect of the fact that shotwell build-depends on libgexiv2-dev; gexiv2 was itself binNMUed as part of the exiv2 transition and I didn't notice the transitive relationship at the time. If the gexiv2 binNMUs hadn't been uploaded for the architecture in question at the time that the shotwell binNMU was built then it would have built against libexiv2-9 directly and a gexiv2 which was still built against libexiv2-6. I've scheduled another binNMU for shotwell on i386 and each of the other architectures which appear to have been affected, which should now pull in the gexiv2 binNMUs depending on libexiv2-9. Regards, Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
