Hi, * Sylvestre Ledru ([email protected]) [140927 20:10]: > On 26/09/2014 17:52, Helmut Grohne wrote: > > Package: libclang1-3.5 > > Version: 1:3.5-2 > > Severity: serious > > Control: affects -1 doxygen > > > > Dear clang maintainers, > > > > I noticed that installing doxygen in a fresh sid chroot results in an > > unusable binary: > > > > $ doxygen > > doxygen: error while loading shared libraries: libclang.so.1: cannot open > > shared object file: No such file or directory > > $ > I am sorry about that. I have a build running which should fix that. > I will let you know later today.
Helmut pointed out on IRC that the symlink from from libclang-3.5.so.1 to /usr/lib/`dpkg-architecture -qDEB_BUILD_MULTIARCH`/libclang.so.1 is missing if the package libclang1 is installed. My investigation pointed to the fact that the file installed in /usr/lib/(arch)/libclang-3.5.so.1 has now the soname libclang-3.5.so and not anymore libclang.so.1. So the ldconfig-call in postinst doesn't create the symlink from libclang.so.1 to libclang-3.5.so.1 anymore. The probably best fix for that would be to go back to the previous soname if there is no strong reason against. Otherwise changing soname means that a new library package should be created, but as we are already past transition time for the next release, that would be better early in the next cycle. (If a new library package is created, binNMUs are possible to replace the binary packages with links to the new library package. As it is now, any package built against libclang1 will become unusable in testing if it migrates on its own, and has wrong and broken dependencies.) Andi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
