Package: debhelper Version: 9.20120322 Severity: normal In my package fai I have some examples which will go into the fai-doc package. Some examples are located in the directory <sourcedir>/examples/simple/scripts/DEBIAN/.
Since dh_md5sums ignores all files in DEBIAN/ lintian prints me a warning. From the build log: . . dh_lintian dh_installdeb dh_gencontrol dh_md5sums -x dh_builddeb dpkg-deb: building package `fai-client' in `../fai-client_4.0~beta7_all.deb'. dpkg-deb: building package `fai-doc' in `../fai-doc_4.0~beta7_all.deb'. . . dpkg-genchanges >../fai_4.0~beta7_amd64.changes dpkg-genchanges: including full source code in upload dpkg-source -i -I --after-build fai-4.0 dpkg-buildpackage: full upload; Debian-native package (full source is included) Now running lintian... . . . W: fai-doc: file-missing-in-md5sums usr/share/doc/fai-doc/examples/simple/scripts/DEBIAN/40-misc W: fai-doc: file-missing-in-md5sums usr/share/doc/fai-doc/examples/simple/scripts/DEBIAN/30-interface W: fai-doc: file-missing-in-md5sums usr/share/doc/fai-doc/examples/simple/scripts/DEBIAN/10-rootpw W: fai-doc: file-missing-in-md5sums usr/share/doc/fai-doc/examples/simple/scripts/DEBIAN/10-keymap IMO dh_md5sums should not ignore all DEBIAN/ subdirectories, but only $tmp/DEBIAN. A patch should change the regex in this line my $find="find . -type f $exclude ! -regex '.*/DEBIAN/.*' -printf '%P\\0'"; -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 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 debhelper depends on: ii binutils 2.22-6 ii dpkg-dev 1.16.2 ii file 5.11-1 ii html2text 1.3.2a-15 ii man-db 2.6.1-1 ii perl 5.14.2-9 ii po-debconf 1.0.16+nmu2 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 0.60 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
