Source: perdition Version: 2.2-3.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie
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. > -I../../.. -I../../../ -I../../../perdition -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o perditiondb_nis.lo perditiondb_nis.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../ > -I../../../perdition -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c perditiondb_nis.c -fPIC -DPIC -o > .libs/perditiondb_nis.o > In file included from perditiondb_nis.c:32: > perditiondb_nis.h:32:10: fatal error: rpcsvc/ypclnt.h: No such file or > directory > 32 | #include <rpcsvc/ypclnt.h> > | ^~~~~~~~~~~~~~~~~ > compilation terminated. > make[5]: *** [Makefile:499: perditiondb_nis.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/perdition_2.2-3.2_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.