Source: moonshot-ui Version: 1.1.0+libsecret~1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -pthread -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 -include config.h > -DLOCALEDIR=\""/usr/share/locale"\" > -DMOONSHOT_FLATSTORE_USERS='"/etc/moonshot/flatstore-users"' -I./libmoonshot > -I./libmoonshot -pthread -I/usr/include/libsecret-1 -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 > -DMOONSHOT_DBUS_BUS_CONF='"/usr/share/moonshot-ui/dbus/org.janet.Moonshot.conf"' > -DMOONSHOT_DBUS_DAEMON='"/usr/bin/dbus-daemon"' -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O0 -Wall -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > libmoonshot/libmoonshot_la-libmoonshot-dbus.lo `test -f > 'libmoonshot/libmoonshot-dbus.c' || echo './'`libmoonshot/libmoonshot-dbus.c > libmoonshot.vapi:45.34-45.56: error: Inline allocated array as parameter > requires to have fixed length > string rules_patterns[], > ^^^^^^^^^^^^^^^^^^^^^^^ > libmoonshot.vapi:46.34-46.62: error: Inline allocated array as parameter > requires to have fixed length > string rules_always_confirm[], > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > libmoonshot.vapi:47.34-47.50: error: Inline allocated array as parameter > requires to have fixed length > string services[], > ^^^^^^^^^^^^^^^^^ > Compilation failed: 3 error(s), 2 warning(s) > make[4]: *** [Makefile:1932: src_moonshot_webp_vala.stamp] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/moonshot-ui_1.1.0+libsecret~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.
