Hi Guillem, thanks for the quick reply!
> > 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? ;) well -- as I have mentioned, it is a non-free package (not even in Debian's non-free yet) which provides pre-built binary blobs (extensions), which on their own are redistributable, but that library is not. So it is upstream who builds/links against them -- I was just wrapping them into a convenience non-free package. > > --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. right -- thanks for chewing it up for me ;) now I read it correctly ;) > 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. I agree that it might lead to completely broken packages and generally should not be used. But in some cases (like mine) for non-free packages I see this option being useful. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
