Source: db1-compat
Version: 2.1.3-24
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):
> cc -I. -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 -Wl,-z,relro \
>       -o db_dump185/db_dump185 db_dump185/db_dump185.c libdb1.so.2
> db_dump185/db_dump185.c: In function ‘main’:
> db_dump185/db_dump185.c:190:22: error: implicit declaration of function 
> ‘getopt’; did you mean ‘getsubopt’? [-Werror=implicit-function-declaration]
>   190 |         while ((ch = getopt(argc, argv, "f:p")) != EOF)
>       |                      ^~~~~~
>       |                      getsubopt
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:40: db_dump185/db_dump185] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/db1-compat_2.1.3-24_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.

Reply via email to