Source: xiphos Version: 4.2.1+dfsg1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs
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/main && /usr/bin/c++ > -DHAVE_CONFIG_H -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu > -I/<<PKGBUILDDIR>>/src -I/<<PKGBUILDDIR>>/src/main/Threads::Threads > -I/<<PKGBUILDDIR>>/src/main/PkgConfig::Core > -I/<<PKGBUILDDIR>>/src/main/PkgConfig::Gtk > -I/<<PKGBUILDDIR>>/src/main/PkgConfig::Gnome > -I/<<PKGBUILDDIR>>/src/main/PkgConfig::Sword > -I/<<PKGBUILDDIR>>/src/main/PkgConfig::Biblesync -isystem > /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include > -isystem /usr/include/uuid -isystem /usr/include/webkitgtk-4.0 -isystem > /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem > /usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem > /usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 > -isystem /usr/include/cairo -isystem /usr/include/pango-1.0 -isystem > /usr/include/harfbuzz -isystem /usr/include/fribidi -isystem > /usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem > /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem > /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libsoup-2.4 -isystem > /usr/include/libxml2 -isystem /usr/include/libmount -isystem > /usr/include/blkid -isystem /usr/include/minizip -isystem /usr/include/sword > -isystem /usr/include/biblesync -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fno-delete-null-pointer-checks -pthread -MD -MT > src/main/CMakeFiles/main.dir/display.cc.o -MF > CMakeFiles/main.dir/display.cc.o.d -o CMakeFiles/main.dir/display.cc.o -c > /<<PKGBUILDDIR>>/src/main/display.cc > [ 17%] Generating da.gmo > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/da.gmo > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/da.po > [ 17%] Generating de.gmo > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/de.gmo > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/de.po > [ 18%] Generating en_GB.gmo > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/en_GB.gmo > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/en_GB.po > [ 18%] Generating es.gmo > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/es.gmo > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/es.po > [ 19%] Generating fa.gmo > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/fa.gmo > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/po/fa.po > In file included from /usr/include/glib-2.0/glib/glib-typeof.h:39, > from /usr/include/glib-2.0/glib/gatomic.h:28, > from /usr/include/glib-2.0/glib/gthread.h:32, > from /usr/include/glib-2.0/glib/gasyncqueue.h:32, > from /usr/include/glib-2.0/glib.h:32, > from /usr/include/gtk-3.0/gdk/gdkconfig.h:13, > from /usr/include/gtk-3.0/gdk/gdk.h:30, > from /usr/include/gtk-3.0/gtk/gtk.h:30, > from /<<PKGBUILDDIR>>/src/main/sword.h:28, > from /<<PKGBUILDDIR>>/src/main/configs.cc:28: > /usr/include/c++/11/type_traits:44:3: error: template with C linkage > 44 | template<typename... _Elements> > | ^~~~~~~~ > In file included from /<<PKGBUILDDIR>>/src/main/configs.cc:28: > /<<PKGBUILDDIR>>/src/main/sword.h:26:1: note: ‘extern "C"’ linkage started > here > 26 | extern "C" { > | ^~~~~~~~~~ The full build log is available from: http://qa-logs.debian.net/2021/10/23/xiphos_4.2.1+dfsg1-5_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.