Source: runawk
Version: 1.6.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=mkcmake
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>    dh_update_autotools_config -O--buildsystem=mkcmake
>    dh_auto_configure -O--buildsystem=mkcmake
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>    dh_auto_build -O--buildsystem=mkcmake
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>       mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
> SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
> LIBEXECDIR=/usr/lib/x86_64-linux-gnu
> ==================================================
> all ===> runawk
> checking C compiler type... gcc 10.2.1
> bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
> 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" 
> utility'
> *** Error code 1
> dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
> INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
> LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu 
> returned exit code 1
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/runawk_1.6.0-2_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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to