Bug#707180: lintian: please include the reverse of python-depends-but-no-python-helper
Package: lintian
Version: 2.5.10.5
Severity: wishlist
It would be great to have a lintian check that is the reverse of
python-depends-but-no-python-helper. That is, a lintian check that is
python-helper-but-no-python-depends.
Please see the discussion here for background:
http://lists.alioth.debian.org/pipermail/python-modules-team/2013-April/015358.html
The concern is that some packages use dh's python2 helper but do not
mention ${python:Depends} in the Depends: clause of a created binary
package.
To avoid false positives, the current suggestion (thanks to jakub
wilk) is:
> I think Lintian should emit the tag only if none of the binary packages
> have ${python:Depends}. This is not bulletproof, but should catch most
> mistakes.
Thanks for lintian,
--dkg
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lintian depends on:
ii binutils 2.22-8
ii bzip2 1.0.6-4
ii diffstat 1.55-3
ii file 1:5.11-3
ii gettext 0.18.1.1-10
ii hardening-includes 2.3
ii intltool-debian 0.35.0+20060710.1
ii libapt-pkg-perl 0.1.27
ii libarchive-zip-perl 1.30-6
ii libc-bin 2.13-38
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.31-1+b2
ii libdpkg-perl 1.16.10
ii libemail-valid-perl 0.190-1
ii libipc-run-perl 0.92-1
ii libparse-debianchangelog-perl 1.2.0-1
ii libtimedate-perl 1.2000-1
ii liburi-perl 1.60-1
ii locales 2.13-38
ii man-db 2.6.3-3
ii patchutils 0.3.2-1.1
ii perl [libdigest-sha-perl] 5.14.2-21
lintian recommends no packages.
Versions of packages lintian suggests:
pn binutils-multiarch <none>
ii dpkg-dev 1.16.10
ii libhtml-parser-perl 3.69-2
pn libperlio-gzip-perl <none>
ii libtext-template-perl 1.45-2
ii man-db 2.6.3-3
ii xz-utils [lzma] 5.1.1alpha+20120614-2
-- debconf-show failed
Reply to: