On Wed, Jun 10, 2020 at 8:25 PM Qianqian Fang wrote:dpkg-shlibdeps: warning: symbol deflateBound used by debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the libraries although, I've already added zlib1g-dev to Build-Depends and zlib1g to the Depends fields, I am wondering what else do I need to add.The libzmat1.so.1 library needs to link against libz.so too. Probably this needs to be fixed upstream.
hi Paul,
I listed zlib1g in the Depends section, isn't it the
provider of libz.so?
https://packages.debian.org/buster/amd64/zlib1g/filelist
These precompiled binaries should be removed from the upstream source repository and tarballs and always built from source at build time. If upstream refuses to do that, you should remove them from the orig.tar.gz before uploading your package. Using the Files-Excluded feature of uscan is a reasonable way to achieve that.
I am the upstream author of this toolbox. I included those
precompiled
mex files because most of my users do not have a dev environment
to compile.
I will remove them from the orig tarball then.
The source package name should be the same as the upstream source repository name (so zmat) and the binary package name should be named after the SONAME of the library binary (so libzmat1).
Boyuan in an earlier message suggested to use libzmat instead of libzmat1. I've changed my control files on salsa
https://salsa.debian.org/fangq/libzmat
moving forward, to make these suggested changes, do I need to reupload the package to mentors?
thanks
Qianqian