Bug#966951: libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1

[Simon McVittie]

Control: clone -1 -2
Control: retitle -1 libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found
Control: reassign -1 libpeas 1.26.0-2
Control: tags -1 = ftbfs pending
Control: severity -2 normal
Control: retitle -2 meson: gnome module stopped generating uninstalled typelib depended on by an executable
Control: reassign -2 meson 0.55.0-2
Control: forwarded -2 https://github.com/mesonbuild/meson/issues/7756
Control: tags -2 = upstream

On Mon, 03 Aug 2020 at 13:09:55 +0100, Simon McVittie wrote:
> I've confirmed that this succeeds in a pure bullseye chroot and fails if
> I upgrade meson (only) to the version from unstable. I'm not completely
> sure whether this is a straightforward regression in meson, or whether
> libpeas is holding it wrong.

I'm still not sure whose bug this is, but I've found a workaround that
libpeas can use (or a fix that can be applied, depending whether this
is considered to be a bug in Meson or in libpeas).

I'll close the original FTBFS report by fixing or working around this in
libpeas; I'm cloning it as a non-RC Meson bug report for investigation
of whether Meson is doing the wrong thing.

Please see the upstream Meson bug for more details and a somewhat
minimal reproducer.

Thanks,
    smcv