Source: libt3key Version: 0.2.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > `pkg-config --cflags tinfo` -c -o .config.o .config.c > .config.c: In function ‘main’: > .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you > mean ‘set_term’? [-Werror=implicit-function-declaration] > 8 | if (setupterm(NULL, fd, &error) == OK) { > | ^~~~~~~~~ > | set_term > .config.c:12:17: error: implicit declaration of function ‘tputs’; did you > mean ‘puts’? [-Werror=implicit-function-declaration] > 12 | tputs("\033[0m", 1, putchar); > | ^~~~~ > | puts > cc1: some warnings being treated as errors > make[2]: *** [.Makefile:19: .config.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libt3key_0.2.10-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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 mark 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.
