This example script uses a relative path to locate its interpreter.
This path will be taken relative to the caller's current directory, not
the script's, so a user will probably not be able to run the example
without modification. This tag can also be caused by script headers like
#!@BASH@, which usually mean that the examples were copied out
of the source tree before proper Autoconf path substitution.
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 131c0f4. For merge requests, please use the latest version in the Lintian check scripts.