Source: smartlist
Version: 3.15-25
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>/src'
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  multigram.c
> multigram.c:71:8: warning: type defaults to ‘int’ in declaration of 
> ‘remov_delim’ [-Wimplicit-int]
>    71 | static remov_delim,maxgram;
>       |        ^~~~~~~~~~~
> multigram.c:71:20: warning: type defaults to ‘int’ in declaration of 
> ‘maxgram’ [-Wimplicit-int]
>    71 | static remov_delim,maxgram;
>       |                    ^~~~~~~
> multigram.c:78:8: warning: type defaults to ‘int’ in declaration of 
> ‘tcguessed’ [-Wimplicit-int]
>    78 | static tcguessed;
>       |        ^~~~~~~~~
> multigram.c: In function ‘matchgram’:
> multigram.c:269:15: warning: type defaults to ‘int’ in declaration of 
> ‘lmeter’ [-Wimplicit-int]
>   269 |    { register lmeter=0;size_t cmaxlen=maxlen;
>       |               ^~~~~~
> In file included from multigram.c:25:
> multigram.c: In function ‘main’:
> includes.h:369:25: warning: ignoring return value of ‘setregid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   369 | #define setrgid(gid)    setregid(gid,-1)
>       |                         ^~~~~~~~~~~~~~~~
> multigram.c:360:15: note: in expansion of macro ‘setrgid’
>   360 |               
> setrgid(pass->pw_gid);error=setgid(pass->pw_gid);setruid(euid);
>       |               ^~~~~~~
> includes.h:370:25: warning: ignoring return value of ‘setreuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   370 | #define setruid(uid)    setreuid(uid,-1)
>       |                         ^~~~~~~~~~~~~~~~
> multigram.c:360:64: note: in expansion of macro ‘setruid’
>   360 |               
> setrgid(pass->pw_gid);error=setgid(pass->pw_gid);setruid(euid);
>       |                                                                ^~~~~~~
> multigram.c:397:50: warning: ignoring return value of ‘chdir’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   397 |                  pmexec[1]=RCMAIN,Endpmexec(2)=0,chdir(defdir);
>       |                                                  ^~~~~~~~~~~~~
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  sublib.c
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  ecommon.c
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  mcommon.c
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  hsort.c
> gcc -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  lastdirsep.c
> gcc -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  multigram.o 
> sublib.o ecommon.o mcommon.o hsort.o lastdirsep.o -o multigram -Wl,-z,relro   
> -lm -lc
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/src'
> /<<PKGBUILDDIR>>/debian/tmp/var/list is owned by uid 1001!=list, please fix 
> this first
> make: *** [debian/rules:47: binary-arch] Error 64


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/smartlist_3.15-25_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.

Reply via email to