Source: doxygen
Version: 1.8.20-4
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/build'
> [100%] Generating Doxygen Manual PDF.
> cd /<<PKGBUILDDIR>>/build/latex && /usr/bin/cmake -E remove refman.tex
> cd /<<PKGBUILDDIR>>/build/latex && /usr/bin/cmake -E copy 
> /<<PKGBUILDDIR>>/build/doc/doxygen_manual.tex .
> cd /<<PKGBUILDDIR>>/build/latex && /usr/bin/cmake -E copy 
> /<<PKGBUILDDIR>>/build/doc/manual.sty .
> cd /<<PKGBUILDDIR>>/build/latex && /usr/bin/cmake -E copy 
> /<<PKGBUILDDIR>>/doc/doxygen_logo.pdf .
> cd /<<PKGBUILDDIR>>/build/latex && faketime @1601634720 /usr/bin/pdflatex 
> -shell-escape doxygen_manual.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdflatex)
>  \write18 enabled.
> entering extended mode
> (./doxygen_manual.tex
> LaTeX2e <2020-10-01> patch level 2
> L3 programming layer <2020-10-27> xparse <2020-03-03>
> 
> /usr/bin/pdflatex: Not writing to 
> ../html/examples/group/latex//group__group2.aux (openout_any = p).
> make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:81: 
> doc/CMakeFiles/doxygen_pdf] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/doxygen_1.8.20-4_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