Package: debhelper Version: 7.2.14 Severity: normal This problem came up on debian-mentors from warnings of:
dpkg-shlibdeps: warning: binaries to analyze should already be installed in their package's directory. from dh_shlibdeps. After a bit of investigation, we tracked it down to the package build directory under debian not having a DEBIAN subdirectory, which made dpkg-shlibdeps think it wasn't a package directory. Changing the sequence of dh_* programs so that dh_installdeb was run before dh_shlibdeps fixed the problem (but that's not the right general solution, I suspect, since package.shlibs should override dh_shlibdeps). When using dh, this problem doesn't occur, but that appears to be by accident. dh_installdebconf always creates the DEBIAN directory in the package build directories even if the package doesn't use debconf, so when using the dh calling sequence, DEBIAN is always created by the time dh_shlibdeps runs. I think having dh_shlibdeps create the DEBIAN directory would resolve the problem. I also noticed, when looking at this, that dh_makeshlibs seems to assume that the DEBIAN directory already exists but doesn't create it. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debhelper depends on: ii binutils 2.19.1-1 The GNU assembler, linker and bina ii dpkg-dev 1.15.2 Debian package development tools ii file 5.03-1 Determines file type using "magic" ii html2text 1.3.2a-14 advanced HTML to text converter ii man-db 2.5.5-2 on-line manual pager ii perl 5.10.0-23 Larry Wall's Practical Extraction ii po-debconf 1.0.16 tool for managing templates file t debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 0.48 tool that converts source archives -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
