Bug#971102: apvlv: FTBFS: ApvlvPdf.cc:32:10: fatal error: goo/gtypes.h: No such file or directory
Source: apvlv
Version: 0.1.5+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DAPVLV_WITH_TXT -DDOCDIR=\"/usr/share/doc/apvlv\" -DPACKAGE_BUGREPORT="\"Alf <naihe2010@126.com>\"" -DPACKAGE_NAME=\"apvlv\" -DPACKAGE_VERSION=\"0.1.5\" -DRELEASE=\"rel\" -DSYSCONFDIR=\"/etc\" -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/poppler/glib -I/usr/include/poppler -O2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/apvlv.dir/ApvlvPdf.cc.o -c /<<PKGBUILDDIR>>/src/ApvlvPdf.cc
> /<<PKGBUILDDIR>>/src/ApvlvPdf.cc:32:10: fatal error: goo/gtypes.h: No such file or directory
> 32 | #include <goo/gtypes.h>
> | ^~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [src/CMakeFiles/apvlv.dir/build.make:150: src/CMakeFiles/apvlv.dir/ApvlvPdf.cc.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/apvlv_0.1.5+dfsg-3_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.
Reply to: