Bug#1002221: apt-dpkg-ref: FTBFS: dvips: DVI file can't be opened: apt-dpkg-ref.dvi: No such file or directory
Source: apt-dpkg-ref
Version: 5.3.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> /<<PKGBUILDDIR>>/make-docs
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> This is SBCL 2.1.11.debian, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/>.
>
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses. See the CREDITS and COPYING files in the
> distribution for more information.
> * INTERLEAVE
> * REFERENCE-GUIDE-LATEX
> * REFERENCE-GUIDE-HTML
> * APT-DPKG-REF
> * OUTPUT-DOCUMENT
> * NIL
> * NIL
> * /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) (preloaded format=latex)
> restricted \write18 enabled.
> entering extended mode
> (./apt-dpkg-ref.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2021-11-22>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def
> ! Argument of < has an extra }.
> <inserted text>
> \par
> l.133 >
> > ~
> ?
> ! Emergency stop.
> <inserted text>
> \par
> l.133 >
> > ~
> No pages of output.
> Transcript written on apt-dpkg-ref.log.
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./apt-dpkg-ref.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2021-11-22>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def
> ! Argument of < has an extra }.
> <inserted text>
> \par
> l.167 >
> > ~
> ?
> ! Emergency stop.
> <inserted text>
> \par
> l.167 >
> > ~
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on apt-dpkg-ref.log.
> This is dvips(k) 2021.1 (TeX Live 2022/dev) Copyright 2021 Radical Eye Software (www.radicaleye.com)
> dvips: DVI file can't be opened: apt-dpkg-ref.dvi: No such file or directory
> make[1]: *** [debian/rules:7: execute_after_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/apt-dpkg-ref_5.3.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 mine
so that we can identify if something relevant changed in the meantime.
Reply to: