Package: src:gcc-11-doc Version: 11.3.0-1 Severity: serious Tags: ftbfs
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: -------------------------------------------------------------------------------- [...] debian/rules build dh build dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_build make[1]: Entering directory '/<<PKGBUILDDIR>>' /usr/bin/make -f debian/Makefile make[2]: Entering directory '/<<PKGBUILDDIR>>' (echo @set version-GCC 11.3.0; \ echo @clear DEVELOPMENT; \ echo @set srcdir `pwd`/gcc ) > gcc/doc/gcc-vers.texi makeinfo -D "fncpp cpp-11" -D "fncppint cppinternals-11" -D "fngcc gcc-11" -D "fngxx g++-11" -D "fngccint gccint-11" -D "fngccinstall gccinstall-11" -D "fngfortran gfortran-11" -D "fntreelang treelang-11" -D "fngnatrm gnat_rm-11" -D "fngnatrmlong GNAT 11 Reference Manual" -D "fngnatugn gnat_ugn-11" -D "fngnatugnlong GNAT 11 User's Guide" -D "fngnatstyle gnat-style-11" -D "fngccgo gccgo-11" -D "fngcov gcov-11" -D "fngcovtool gcov-tool-11" -D "fngcovdump gcov-dump-11" -D "fnlibgomp libgomp-11" -D "fnlibitm libitm-11" -D "fnlibquadmath libquadmath-11" -D "fnltodump lto-dump-11" -D "BUGURL http://bugs.debian.org/"; --no-split -Igcc/doc -Igcc/doc/include -o gcc-11.info gcc/doc/gcc.texi extend.texi:2490: @itemx should not begin @table make[2]: *** [debian/Makefile:113: gcc-11.info] Error 1 make[2]: Leaving directory '/<<PKGBUILDDIR>>' make[1]: *** [debian/rules:58: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:55: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202312/ About the archive rebuild: The build was made using virtual machines from AWS, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
