[Pkg-telepathy-maintainers] Bug#963311: telepathy-glib: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: telepathy-glib
Version: 0.24.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> tp_verify_true
> ^^^ Undeclared symbols
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/docs/reference'
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/docs/reference'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/docs'
> make[3]: Nothing to be done for 'check-am'.
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/docs'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> make  check-local
> make[3]: Entering directory '/<<PKGBUILDDIR>>'
> egrep -A 5 '[F]IXME|[T]ODO|[X]XX' ./telepathy-glib/*.[ch] \
> 	> FIXME.out || true
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/telepathy-glib_0.24.1-2_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.