Bug#952252: wpebackend-fdo: FTBFS: /bin/sh: 1: client-header: not found

[Lucas Nussbaum]

Source: wpebackend-fdo
Version: 1.4.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> [  6%] Generating bridge/wpe-bridge-protocol.c, bridge/wpe-bridge-client-protocol.h, bridge/wpe-bridge-server-protocol.h
> < /<<PKGBUILDDIR>>/src/bridge/wpe-bridge.xml > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bridge/wpe-bridge-protocol.c
> client-header < /<<PKGBUILDDIR>>/src/bridge/wpe-bridge.xml > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bridge/wpe-bridge-client-protocol.h
> /bin/sh: 1: client-header: not found
> make[3]: *** [CMakeFiles/WPEBackend-fdo.dir/build.make:66: bridge/wpe-bridge-protocol.c] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/wpebackend-fdo_1.4.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.