> Why is the lib installed by code in debian/rules? The upstream build > system should do that and it seems it does that, at least partially.
I'm afraid I don't understand what this means, can you point me to an example? ________________________________________ From: Andrey Rahmatullin <w...@debian.org> Sent: Tuesday, July 25, 2017 5:28:34 PM To: Jørgen Kvalsvik; 866...@bugs.debian.org Subject: Re: Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710] Control: tags -1 + moreinfo Control: retitle -1 RFS: segyio/1.2.0-1 [ITP] Please don't build the Python 2 module, see https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html Please switch to the debhelper compat level 10. ${shlibs:Depends} for -dev packages does nothing and there is a warning about that in the build log. Why is the lib installed by code in debian/rules? The upstream build system should do that and it seems it does that, at least partially. segyio-cath doesn't have a manpage (and lintian tells that). Consider adding the symbols file for the library. -- WBR, wRAR ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorized use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you
