Hi! On Tue, 2013-05-07 at 13:39:01 -0400, Yaroslav Halchenko wrote: > Package: dpkg-dev > Version: 1.16.10 > Severity: normal > File: /usr/bin/dpkg-shlibdeps
> now the same "couldn't find library" message could be warning or error, > e.g. > > dpkg-shlibdeps: warning: couldn't find library libmat.so needed by > debian/matlab-psychtoolbox-3-nonfree/usr/lib/matlab/site/psychtoolbox-3/WaitSecs.mexa64 > (ELF format: 'elf64-x86-64'; RPATH: '') > dpkg-shlibdeps: error: couldn't find library libeyelink_core-1.9.so.58 needed > by > debian/matlab-psychtoolbox-3-nonfree/usr/lib/matlab/site/psychtoolbox-3/Eyelink.mexa64 > (ELF format: 'elf64-x86-64'; RPATH: '') > > N.B. this is for some non-free package which relies on users having a shared > library provided manually Well the obvious fix here is to have that library installed at build time. How is the project linking against it otherwise? > and in case of the error the whole run of dpkg-shlibdeps fails without > generating substvars. The situation persists even if I use documented: > > --ignore-missing-info > Do not fail if dependency information can't be found for a shared > library. Usage of this option > is discouraged, all libraries should provide dependency information > (either with shlibs files, > or with symbols files) even if they are not yet used by other > packages. > > which from the description sounds precisely what I need, but in the code is > not > influencing decision to exit with error upon $error_count. This is for an entirely different problem, when there's a shared library but no shlibs or symbol files. Your problem instead is a missing shared library. While another option to ignore such errors could be added, I think I'd rather not, because those are easily fixed by having the library around, and not having it means allowing the possibility of generating pretty broken packages, for no apparent good reason. Given this I'm inclined to close the bug report if no convincing counter-arguments are put forward. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
