weak-library-dev-dependency
The given package appears to be a shared library -dev package, but
the dependency on what seems to be a corresponding shared library package
does not force the same package version. To ensure that compiling and
linking works properly, and that the symlinks in the -dev package point
to the correct files in the shared library package, a -dev package should
normally use (= ${binary:Version}) for the dependency on the
shared library package.
Sometimes, such as for -dev packages that are architecture-independent to
not break binNMUs or when one doesn't want to force a tight dependency, a
weaker dependency is warranted. Something like (>=
${source:Upstream-Version}), (<<
${source:Upstream-Version}+1~), possibly using
${source:Version} instead, is the right approach. The goal is to
ensure that a new upstream version of the library package doesn't satisfy
the -dev package dependency, since the minor version of the shared
library may have changed, breaking the *.so links.
For more information please consult:
- Debian Policy Manual section 8.5
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.108.0
release tag in our Git
repository.
You can find the detection logic for this version at commit a1e47cb. For merge requests, please use the latest version in the Lintian check debian/control.
Visibility: error