The code in
debian/rules requires a prerequisite
that is not presently listed in the package's
In the special case of Python, affected packages should
on one of
python3-all-dev. Which one depends on whether a package supports
multiple Python versions, and also whether the package builds Python modules
or uses Python only as part of the build process.
Packages that depend on a specific Python version may build-depend
on any appropriate
The condition you see in the context is not a recommendation on what to add. If
you see a list, more than likely only one member is needed to make this tag go
away. You probably also do not need the
:any multiarch acceptor,
if you see one.
For more information please consult:
- Package relationships (Section 4.2) in the Debian Policy Manual
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 ea05801. For merge requests, please use the latest version in the Lintian check debian/rules.