The package build-depends on a versioned development package of Berkeley DB (libdbX.Y-dev) instead of versionless package (libdb-dev). Unfortunately this prevents binNMUs when default Berkeley DB version changes.
Unless the package absolutely have to depend on specific Berkeley DB version, it should build-depends on libdb-dev. For more information on the upgrade process, please see the references.
The package can usually be made Berkeley DB version agnostic by the following steps:
- note the version of Berkeley DB used to compile the package on build time
- on first install copy the used version to active version
- on upgrades compare the versions and if they differ do the upgrade procedure
If you are unsure you can contact Berkeley DB maintainer, who would be glad to help.
Should the package have a legitimate reason for using the versioned development package, please add an override.
For more information please consult:
The tag is present in Lintian version
That is the most recent version we know about.
We use semantic versions.
The patch number is a commit step indicator relative to the
release tag in our Git
You can find the detection logic for this version at commit ce6249d. For merge requests, please use the latest version in the Lintian check fields/package-relations.