Your message dated Sat, 13 Nov 2021 23:11:55 +0900 with message-id <YY/hq6vdktl6g...@np-u9310.g01.fujitsu.com> and subject line Re: Bug#998240: texlive: causes lgrind to FTBFS has caused the Debian Bug report #998240, regarding texlive: causes lgrind to FTBFS to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: texlive Version: 2021.20210921-1 Severity: serious Tags: sid bookworm Control: affects -1 + src:lgrind Hi, lgrind recently started to FTBFS: latex lgrind.dtx 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 (./lgrind.dtx LaTeX2e <2021-06-01> patch level 1 L3 programming layer <2021-08-27> (/usr/share/texlive/texmf-dist/tex/latex/base/ltxdoc.cls Document Class: ltxdoc 2020/12/05 v2.1b Standard LaTeX documentation class (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2021/02/12 v1.4n Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty))) Writing index file lgrind.idx Writing glossary file lgrind.glo (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def) No file lgrind.aux. (./lgrind.dtx [1] [2] [3] [4] [5] (/usr/share/texlive/texmf-dist/tex/latex/base/ts1cmtt.fd) [6] [7] LaTeX Warning: Reference `underscore' on page 8 undefined on input line 461. [8] ! Missing } inserted. <inserted text> } l.540 % \item[\^] The beginning of a line ? ! Emergency stop. <inserted text> } l.540 % \item[\^] The beginning of a line Output written on lgrind.dvi (8 pages, 27616 bytes). Transcript written on lgrind.log. make: *** [debian/rules:13: build-stamp] Error 1 The offending line + some context: 537 % The meta-symbols and their meanings are: 538 % \begin{description} 539 % \item[\$] The end of a line 540 % \item[\^] The beginning of a line 541 % \item[$\backslash$d] A delimiter (space, tab, newline, start of line) 542 % \item[$\backslash$a] Matches any string of symbols (like `.*' in lex) 543 % \item[$\backslash$p] Matches any identifier. In a procedure definition I'm not sure which package is responsible for that ... starting with 'texlive' which is the only relevant B-D of lgrind. Please reassign as needed. Andreas
lgrind_3.67-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Hi Andreas, > Fixed lgrind uploaded. Feel free to close the bug if you don't want to look > into the regression and rather consider lgrinds usage of '\^' without any > (empty) argument as buggy. We have fixed lgrind's rather "unusual" use of TeX before. This is a common problem with packages thatuse unsupported - but at a certain time working - constructs that later on stopped working. So with lgrind fixed, I am closing this bug. Thanks to Hilmar for the fix! Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
--- End Message ---
