[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

weak-library-dev-dependency is there a lintian bug ?

Hello I am developping a package for the tango control system.

the upstream tango-7.1.1.tar.gz contain in fact a sub package.
in the configure.in there is a 

this sub package provide a librairy but the version number is taken from its
AC_INIT with this line in the debian/rule file:

LOG4TANGO_VERSION := $(shell egrep AC_INIT lib/cpp/log4tango/configure.in | cut -f 2 -d ' ' | cut -f 1 -d ',')
DEB_NOREVISION_VERSION := $(shell dpkg-parsechangelog | egrep '^Version:' | cut -f 2 -d ' ' | cut -f 2 -d '-')

for now the version is 4.0.3-1 != (= ${binary:Version})

So to generate the right package verison number I am doing this:
in the control file I put:

Package: liblog4tango4-dev
Section: libdevel
Architecture: any
Depends: liblog4tango4 (= ${RELUP}), ${misc:Depends}

then I pass the RELUP variable to dh_gencontrol during the build

dh_gencontrol -pliblog4tango4 -- -v$(LOG4TANGO_VERSION)-$(DEB_NOREVISION_VERSION)

It works fine but now lintian complaining about this (= ${RELUP})

here the lintian error

E: tango source: weak-library-dev-dependency liblog4tango4-dev on liblog4tango4 (= ${RELUP})
N:    The given package appears to be a shared library -dev package, but the
N:    dependency on what seems to be a corresponding shared library package
N:    does not force the same package version. To ensure that compiling and
N:    linking works properly, and that the symlinks in the -dev package point
N:    to the correct files in the shared library package, a -dev package
N:    should normally use (= ${binary:Version}) with the dependency on the
N:    shared library package.
N:    If the -dev package is architecture-independent, it cannot use this
N:    dependency since it would break binary NMUs. Instead, a dependency of
N:    (>= ${source:Upstream-Version}), ( or similar is usually the correct
N:    approach.
N:    Refer to Debian Policy Manual section 8.5 (Dependencies between the
N:    packages of the same library) for details.
N:    Severity: important, Certainty: possible

So now the question, is it a lintian bug or must I change something to solve this "issue".



GPG public key   1024D/A59B1171 2009-08-11
    fingerprint = 1688 A3D6 F0BD E4DF 2E6B  06AA B6A9 BA6A A59B 1171
uid  Picca Frédéric-Emmanuel <picca@synchrotron-soleil.fr>

Attachment: signature.asc
Description: PGP signature

Reply to: