Package: debhelper
Version: 13.11.4
Tags: trixie sid
Severity: normal
X-Debbugs-Cc: me...@packages.debian.org
Control: affects -1 + src:meson
As a result of upstream changes in meson, rebuilding libgit2-glib with
meson >= 1.2.0 results in the installed tree in debian/tmp containing
usr/lib/python3/dist-packages/gi/overrides/__pycache__/Ggit.cpython-311.pyc,
which didn't happen with previous versions. Depending on the package,
this will either cause FTBFS (because the .pyc file isn't matched by
any .install file) or a package containing undesired .pyc files (which
as it happens is what happens in libgit2-glib).
This can be turned off by passing -Dpython.bytecompile=-1 to `meson setup`.
As far as I'm aware, we never want to include .pyc in Debian packages,
so I think debhelper's meson build system plugin should be turning this off
as a standard setting for all Debian packages (similar to the way it
sets --prefix=/usr as a standard setting for all Debian packages).
Do the Meson maintainers agree?
Is there a way this can be done, without making packages FTBFS if debhelper
is backported to an older suite but Meson is not? -Dpython.bytecompile=-1
will cause `meson setup` to fail if Meson is an older version, and I'm not
aware of a way to say "set this option if supported, ignore if not" without
parsing `meson --version` and comparing it with a threshold.
smcv
