Package: lintian Version: 2.114.0 Severity: wishlist I discovered that in several of my autopkgtest scripts, and in various other packages in the archive, the following pattern appears:
... cd somewhere ... for py in $(py3versions -r 2>/dev/null) ... Unfortunately, this silently fails, as no python versions are returned when py3versions -r is run from anywhere other than the top directory of an unpacked source, and only the error message: py3versions: error parsing Python3-Version attribute is given. The "2>/dev/null" is nevertheless usually required even when run from the correct directory to silence the warning: py3versions: no X-Python3-Version in control file, using supported versions which appears on most packages. The corrected script should read something like: ... for py in $(py3versions -r 2>/dev/null); do cd somewhere ... or ... python3_versions=$(py3versions -r 2>/dev/null) cd somewhere ... for py in $python3_versions; do ... A regex such as /\bcd\b.*py3versions\s+-r/s applied to the entire content of debian/tests/control and every other file in debian/tests should catch this issue. Best wishes, Julian