[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#867035: context: fatal file format error



On 03.07.17 17:43, Sanjoy Mahajan wrote:

Hi Sanjoy,

Sorry late response. Your E-Mail did not make to the mailing list, b/c
it breached the 100k limit.

> context fails with "(Fatal format file error; I'm stymied)".  Here the
> log from a minimal example, with test.tex as
> 
>   \starttext
>   \input knuth
>   \stoptext
> 
> Here's the end of the output showing the error:
> 
>   mtx-context     | run 1: luatex --fmt="/var/lib/texmf/luatex-cache/context/b47c3d3cee7cb6c86268d0595268c442/formats/luatex/cont-en" --jobname="test" --lua="/var/lib/texmf/luatex-cache/context/b47c3d3cee7cb6c86268d0595268c442/formats/luatex/cont-en.lui" --no-parse-first-line --c:currentrun=1 --c:fulljobname="./test.tex" --c:input="./test.tex" --c:kindofrun=1 --c:maxnofruns=9 "cont-yes.mkiv"
>   This is LuaTeX, Version 1.0.4 (TeX Live 2017/Debian) 
>    system commands enabled.
> 
>   (Fatal format file error; I'm stymied)
>   mtx-context     | fatal error: return code: 1
> 
> The full log is attached.
> 
> I think that the problem happens because context is still at 2016
> whereas texlive-binaries recently became 2017.  I'm running a mostly
> testing system, and texlive-binaries 2017 made it out of unstable into
> testing, but the newer, 2017 context hasn't made it out of unstable.
> 
> As a test of this guess, on my other laptop (also Debian/amd64/mostly
> testing), which has the same problem as reported here, I did
> 
>   $ apt -t unstable install context
> 
> which brought in zillions of texlive packages, and reran context on
> test.tex -- with no problem.  I also reran it on my current book project
> (about 100 pages so far), and it also worked.
> 
Thanks for your analysis! Currently all packages in Debian testing seem
to be consistent. So I'd assume that your issue is gone. Can we close
that bug now?

Hilmar
-- 
#206401 http://counter.li.org

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: