Package: linda
Version: 0.3.13
Severity: wishlist

When run against the OpenAFS kernel module package built from
openafs-modules-source, linda reports:

W: openafs-modules-2.4.28; There is no Depends: line in the control file.
 The package has no Depends: line in the control file. This is not
 allowed by Policy if the package in question contains binary objects.
 Perhaps try calling dpkg-shlibdeps or dh_shlibdeps in the package
 rules file.

However, this is intentional.  For one, the kernel may not be maintained
using a Debian package at all; the module could have been built against
a hand-compiled kernel.  In my case, the kernel was built with make-kpkg,
but the openafs-modules package only declares a Recommends instead of a
Depends on the kernel to avoid getting into dependency issues in some
cases.

I think the best fix would be to not consider kernel modules to be
"binary objects" for the purposes of this test (perhaps by noticing that
they're in /lib/modules).  The intent of the test is clearly to notice
binaries that don't declare a proper libc dependency; kernel modules are
(nearly) unique in that they don't build against libc.

Incidentally, a reference to the section of policy being referred to here
would be useful; I'm not actually sure what part of policy this message
is intended to point at, unless it's the part about depending on shared
libraries that binaries are linked against.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.30
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages linda depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  dash                          0.5.2-4    The Debian Almquist Shell
ii  file                          4.12-1     Determines file type using "magic"
ii  man-db                        2.4.2-21   The on-line manual pager
ii  python                        2.3.5-1    An interactive high-level object-o

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to