2008/12/6 Eugene V. Lyubimkin <[EMAIL PROTECTED]>: > Raphael Geissert wrote: >> Hi, >> >> Eugene V. Lyubimkin wrote: >> [...] >>> Lintian recently started to produce 'debhelper-but-no-misc-depends' >>> warnings. While it reveal true issues, it also produces false positives >>> in case of data-only packages, which have no 'Depends' field at all. >> >> Could you please give an example? > Ok, here is example: I have two binary packages: 'qorganizer' and > 'qorganizer-translations'. The latter just have 'Recommends' on 'qorganizer' > and no > 'Depends' at all.
is qorganizer-translations of any use all on its own without qorganizer? I think not. The former should depend on the latter. > Moreover, '$ grep-aptavail ! -F Depends " " -s Package' can give you > thousands of another examples. I believe you are getting things wrong. First of all the warning is no emitted just because ${misc:Depends} is not specified, it is only emitted when dh or one of the dh_ commands specifically setting some value for misc:Depends is used in debian/rules. When either 'dh' or CDBS' debhelper.mk are used and ${misc:Depends} is not used in debian/control lintian will always emit the tag because there's no way to know whether one of the multiple dh_ commands called by either of them will end up defining some value for misc:Depends. IMHO this report should be closed as there is no bug. Oh, and: > 'Depends: ${misc:Depends}' will in 99% of my cases result in empty > 'Depends:' line which is Policy violation. No, it won't (unless you are building the package all by yourself without the assistance of dpkg, which is very unlikely to happen as the package would easily break and debhelper would probably not be used either). > > -- > Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com > Ukrainian C++ developer, Debian APT contributor > > Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net Jim Bishop - "Golf is played by twenty million mature American men whose wives think they are out having f... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]