Bonjour Ben, Le sam. 12 nov. 2022 à 23:12, Ben Westover <m...@benthetechguy.net> a écrit : > > Correct me if I'm wrong, but I that believe for backports, keeping it > minimally different from the original package is prioritized over things > like functional tests, docs, etc.
That is correct. > Thus, instead of adding the necessary > dependencies and patching required to make the tests work on bullseye, > I've elected to just build it with the nocheck profile. Currently, without adding at least python3-distutils (and maybe other?) in BD, pcm fails at the dh_auto_configure step with: > ModuleNotFoundError: No module named 'distutils.core' > ../meson.build:31:0: ERROR: <ExternalProgram 'python3' -> > ['/usr/bin/python3']> is not a valid python or it is missing setuptools > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dkeyringd This is easily reproducible with salsa-ci by setting RELEASE to bullseye like I did here: > https://salsa.debian.org/daissi/pacman/-/jobs/3514447 My point is this issue is hidden in sid because python3-distutils is pulled by dependencies, but it (or python3-all) must be added in the Build-Deps of pcm even for sid. Moreover, based on the meson.build, it looks like python3 is not an optional build-deps. Best, Dylan
