Lintian ReportsBETA


This package seems to contain the development files fer a shared library, but the requirement for that shared library to be installed does not include the same version.

A -dev package should normally use (= ${binary:Version}) for the prerequisite on the shared library. That will ensure that programs compile and link properly. The symbolic links for the dynamic linker will also point to the correct places.

To be sure, there are some circumstances when a weak prerequisite is warranted, for example to prevent the breaking of binNMUs with architecture-independent -dev packages. Then something like (>= ${source:Upstream-Version}), (<< ${source:Upstream-Version}+1~) may be the right approach, or possibly ${source:Version} instead. The goal there is to ensure that a new upstream version of the library does not satisfy the prerequisite, since any minor version change might break the *.so links.

For more information please consult:

The tag is present in Lintian version 2.114.163. That is the most recent version we know about.

We use semantic versions. The patch number is a commit step indicator relative to the 2.114.0 release tag in our Git repository.

You can find the detection logic for this version at commit 3410a22. For merge requests, please use the latest version in the Lintian check debian/control/prerequisite/development.

Visibility: error

The following 6 source packages in the archive triggered the tag 7 times (in any Lintian version).

We found 2 overrides. The tag performed 71% of the time.