On Fri, 29 Jul 2022 18:33:25 +0200 Lucas Nussbaum <lu...@debian.org> wrote:
Source: givaro Version: 4.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookwormHi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Parsing file /<<PKGBUILDDIR>>/tests/test-recint_convert.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-recint_exp.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-recint_exp.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-recint_extra.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-recint_extra.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-recint_rand.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-recint_rand.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-regression.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-regression.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-ringarith.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-ringarith.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-rint_arith.C... > Parsing file /<<PKGBUILDDIR>>/tests/test-rint_arith.C... > Preprocessing /<<PKGBUILDDIR>>/tests/test-rmint_arith.C... > Parsing file /<<BUILDDIR>>/g > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/07/28/givaro_4.2.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&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 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.
I think this is really a regression in Doxygen (version 1.9.4 was just uploaded recently). I've reported it at https://github.com/doxygen/doxygen/issues/9491. An hacky fix is to remove the symlinks that are generated by the configure script before building the documentation. I'll upload a new package shortly. Doug
signature.asc
Description: PGP signature
