Source: autolog
Version: 0.42-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
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 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -o autolog autolog.c
> autolog.c: In function ‘check_utmp’:
> autolog.c:320:38: warning: passing argument 1 of ‘ctime’ from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   320 |                                ctime(&utmpp->ut_time));
>       |                                      ^
>       |                                      |
>       |                                      int32_t * {aka int *}
> In file included from autolog.c:64:
> /usr/include/time.h:183:35: note: expected ‘const time_t *’ {aka ‘const long 
> int *’} but argument is of type ‘int32_t *’ {aka ‘int *’}
>   183 | extern char *ctime (const time_t *__timer) __THROW;
>       |                     ~~~~~~~~~~~~~~^~~~~~~
> autolog.c:346:30: warning: passing argument 1 of ‘ctime’ from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   346 |                        ctime(&utmpp->ut_time));
>       |                              ^
>       |                              |
>       |                              int32_t * {aka int *}
> /usr/include/time.h:183:35: note: expected ‘const time_t *’ {aka ‘const long 
> int *’} but argument is of type ‘int32_t *’ {aka ‘int *’}
>   183 | extern char *ctime (const time_t *__timer) __THROW;
>       |                     ~~~~~~~~~~~~~~^~~~~~~
> autolog.c: In function ‘pat_match’:
> autolog.c:613:9: error: implicit declaration of function ‘re_comp’; did you 
> mean ‘regcomp’? [-Werror=implicit-function-declaration]
>   613 |         re_comp(pattern);
>       |         ^~~~~~~
>       |         regcomp
> autolog.c:614:16: error: implicit declaration of function ‘re_exec’; did you 
> mean ‘regexec’? [-Werror=implicit-function-declaration]
>   614 |         return re_exec(strg);
>       |                ^~~~~~~
>       |                regexec
> autolog.c: In function ‘load_users’:
> autolog.c:441:9: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   441 |         fscanf(f, "%d", &userfill);
>       |         ^~~~~~~~~~~~~~~~~~~~~~~~~~
> autolog.c:451:17: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   451 |                 fscanf(f, " %s %d %s %d %d %d %d",
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   452 |                        userlst[userpos].Name,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~
>   453 |                        &userlst[userpos].UserID,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~
>   454 |                        userlst[userpos].Device,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~
>   455 |                        &userlst[userpos].IdleTime,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   456 |                        &userlst[userpos].SessStrt,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   457 |                        &userlst[userpos].Ban_Ends,
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   458 |                        &userlst[userpos].WarnEnds);
>       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> autolog.c: In function ‘get_PIDs’:
> autolog.c:839:9: warning: ignoring return value of ‘fgets’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   839 |         fgets(iline, LINELEN, ps);               /* get header-line */
>       |         ^~~~~~~~~~~~~~~~~~~~~~~~~
> autolog.c: In function ‘mesg’:
> autolog.c:964:25: warning: ignoring return value of ‘system’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   964 |                         system (mbuf);
>       |                         ^~~~~~~~~~~~~
> autolog.c:987:25: warning: ignoring return value of ‘system’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   987 |                         system (mbuf);
>       |                         ^~~~~~~~~~~~~
> autolog.c:1012:25: warning: ignoring return value of ‘system’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1012 |                         system(mbuf);
>       |                         ^~~~~~~~~~~~
> autolog.c: In function ‘kill_lost_PIDs’:
> autolog.c:1167:9: warning: ignoring return value of ‘fgets’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1167 |         fgets(iline, LINELEN, ps);               /* get header-line */
>       |         ^~~~~~~~~~~~~~~~~~~~~~~~~
> autolog.c: In function ‘check_utmp.isra’:
> autolog.c:325:77: warning: ‘%s’ directive output may be truncated writing up 
> to 63 bytes into a region of size 42 [-Wformat-truncation=]
>   325 |                 snprintf(tmp_str, 79, "Can't get status of user's 
> terminal: %s", dev);
>       |                                                                       
>       ^~   ~~~
> In file included from /usr/include/stdio.h:906,
>                  from autolog.c:58:
> In function ‘snprintf’,
>     inlined from ‘check_utmp.isra’ at autolog.c:325:3:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: 
> ‘__builtin___snprintf_chk’ output between 38 and 101 bytes into a destination 
> of size 79
>    54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    55 |                                    __glibc_objsize (__s), __fmt,
>       |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    56 |                                    __va_arg_pack ());
>       |                                    ~~~~~~~~~~~~~~~~~
> autolog.c: In function ‘check_idle’:
> autolog.c:648:44: warning: ‘%s’ directive output may be truncated writing up 
> to 63 bytes into a region of size 59 [-Wformat-truncation=]
>   648 |         snprintf(ddev, sizeof(ddev), "/dev/%s", dev);     /* append 
> /dev/ to base name */
>       |                                            ^~   ~~~
> In function ‘snprintf’,
>     inlined from ‘check_idle’ at autolog.c:648:2:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: 
> ‘__builtin___snprintf_chk’ output between 6 and 69 bytes into a destination 
> of size 64
>    54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    55 |                                    __glibc_objsize (__s), __fmt,
>       |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    56 |                                    __va_arg_pack ());
>       |                                    ~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:15: autolog] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/autolog_0.42-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&[email protected]&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