Lintian tag information: rules-require-build-prerequisite (type: error)

Description (from lintian-explain-tags)

The code in debian/rules requires a prerequisite
that is not presently listed in the package's Build-Depends.

In the special case of Python, affected packages should Build-Depend on
one of python3, python3-all, python3-dev, or 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 pythonX.Y or pythonX.Y-dev package instead.

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
qualifier, if you see one.

Please refer to Package relationships (Section 4.2) in the Debian Policy
Manual for details.

Visibility: error
Show-Always: no
Check: debian/rules
Renamed from: missing-build-dependency missing-python-build-dependency

Affected packages

source version binary tag type tag information count
phonetisaurus 0.7.8-6 error rules-require-build-prerequisite (does not satisfy python2:any | python2-dev:any | python2.7:any | python2.7-dev:any | python3:any | python3-dev:any | python3-all:any | python3-all-dev:any | python3.4:any | python3.4-dev:any | python3.5:any | python3.5-dev:any | python3.6:any | python3.6-dev:any | python3.7:any | python3.7-dev:any) [debian/rules] 1
sequitur-g2p 0+r1668.r3-1 error rules-require-build-prerequisite (does not satisfy python2:any | python2-dev:any | python2.7:any | python2.7-dev:any | python3:any | python3-dev:any | python3-all:any | python3-all-dev:any | python3.4:any | python3.4-dev:any | python3.5:any | python3.5-dev:any | python3.6:any | python3.6-dev:any | python3.7:any | python3.7-dev:any) [debian/rules] 1