Source: pycairo
Version: 1.24.0-1
Severity: important
Tags: ftbfs
X-Debbugs-CC: hel...@subdivi.de
During an archive rebuild against the release candidate for meson in
experimental, pycairo failed to build from source with the following log
excerpt:
```
dh_auto_install -O--buildsystem=meson
cd obj-x86_64-linux-gnu && DESTDIR=/<<PKGBUILDDIR>>/debian/tmp
LC_ALL=C.UTF-8 ninja install
[0/1] Installing files.
Compiling
'/<<PKGBUILDDIR>>/debian/tmp/usr/lib/python3/dist-packages/cairo/__init__.py'...
[...]
Running custom install script '/usr/bin/python3
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/pycompile.py
python-3.11-installed.json 0'
[...]
dh_missing -O--buildsystem=meson
dh_missing: warning:
usr/lib/python3/dist-packages/cairo/__pycache__/__init__.cpython-311.pyc
exists in debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
[...]
make: *** [debian/rules:6: binary] Error 25
```
This fails with the release candidate, but does not fail against the
stable release of meson. The underlying cause is an additional feature
of meson:
https://mesonbuild.com/Release-notes-for-1-2-0.html#python-module-can-now-compile-bytecode
If this file is not desired in the debian package, please specify your
preferred value for this meson setting. For example, to avoid compiling
bytecode as part of `meson install`, you could setup the build system
with the `-Dpython.bytecompile=-1` option.
--
Eli Schwartz
