Source: postgresql-filedump Version: 12.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement > -Werror=vla -Wendif-labels -Wmissing-format-attribute > -Wimplicit-fallthrough=3 -Wformat-security -fno-strict-aliasing -fwrapv > -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation > -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security > -fno-omit-frame-pointer -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -I. -I./ > -I/usr/include/postgresql/13/server -I/usr/include/postgresql/internal > -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -c -o > decode.o decode.c > decode.c:7:10: fatal error: access/tuptoaster.h: No such file or directory > 7 | #include <access/tuptoaster.h> > | ^~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make[2]: *** [<builtin>: decode.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/10/27/postgresql-filedump_12.0-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.
