Lintian Reports

W multi-arch-same-package-calls-pycompile

All reports of multi-arch-same-package-calls-pycompile for the archive. The extended description of this tag is:

This Multi-Arch: same package uses pycompile or py3compile in the specified maintainer script.

py{,3}compile are tools used to byte-compile Python source files. It is typically run on installation of Debian packages that ship Python modules. However, they do not support installing several architectures of the same package and this is not Multi-Arch: safe.

If the contents of the package is not architecture dependent, it should usually be made binary-all.

If the contents of the package is architecture dependent, it should usually get a dependency on the Python interpreter for the same architecture. This is a dependency in the form of python3, not an architecture-qualified dependency such as python3:any (which can be fulfilled by the Python interpreter for any architecture).

If a dependency on the Python interpreter for the same architecture exists (usually generated by dh-python), the Multi-Arch: same has no effect and should be dropped.

Refer to the pycompile(1) manual page, the py3compile(1) manual page, and for details.

Severity: normal, Certainty: possible

Check: scripts, Type: binary

Emitted (non-overridden): 5, overridden: 0, total: 5

The package names link to the relevant maintainer page and the corresponding report for the source package. The links go to the full maintainer report page, which includes info and experimental tags and overridden tags, rather than the default page that shows only errors and warnings.

python-fpylll 0.4.1+ds1-5 (binary) (Debian Python Modules Team <>)

python-lxml 4.4.1-1 (binary) (Matthias Klose <>)

python3-gccjit 0.4-10 (binary) (Matthias Klose <>)

python3-lxml 4.4.1-1 (binary) (Matthias Klose <>)

python3-reprozip 1.0.14-2+b1 (binary) (Debian Science Team <>)