Source: felix-latin Version: 2.0-11.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>/TeX' > xelatex felix34.tex > This is XeTeX, Version 3.14159265-2.6-0.999992 (TeX Live 2020/Debian) > (preloaded format=xelatex) > restricted \write18 enabled. > entering extended mode > (./felix34.tex > LaTeX2e <2020-10-01> patch level 4 > L3 programming layer <2021-01-09> xparse <2020-03-03> > (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls > Document Class: article 2020/04/10 v1.4m Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty > (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty > (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty > (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-xetex.def > (|extractbb --version)) > Runaway argument? > \q_stop <\__int_eval:w \c_zero_int \__int_eval_end: \exp_after:wN \use_ii:nnn > \ > ETC. > ! File ended while scanning use of \__sys_tmp:w. > <inserted text> > \par > l.148 { \sys_load_backend:n { } } > > ? > ! Emergency stop. > <inserted text> > \par > l.148 { \sys_load_backend:n { } } > > No pages of output. > Transcript written on felix34.log. > make[2]: *** [Makefile:3: tout] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/felix-latin_2.0-11.1_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.