Bug#263296: tetex-bin 2.0.2-17 broke "tex --parse-first-line"
On 03.08.04 Benjamin BAYART (bayartb@sitadelle.com) wrote:
> tex --parse-first-line works fine up to version 2.0.2-16, and
> does not work anymore since 2.0.2-17.
>
> result on a 2.0.2-16:
> madflo@rei:/tmp$ tex --parse-first-line x
> This is TeXk, Version 3.14159 (Web2C 7.4.5)
> %&-line parsing enabled.
> (./x.tex
> LaTeX2e <2001/06/01>
> Babel <v3.7h> and hyphenation patterns for american, french, bahasa,
> basque, croatian, czech, danish, dutch, finnish, greek, italian, latin,
> magyar, norsk, norsk, norsk, portuges, romanian, russian, slovak, slovene,
> spanish, turkish, ukr ainian, nohyphenation, loaded.
> (/usr/share/texmf/tex/latex/base/article.cls
> Document Class: article 2001/04/21 v1.4e Standard LaTeX document class
> (/usr/share/texmf/tex/latex/base/size10.clo)) (./x.aux) [1] (./x.aux) )
> Output written on x.dvi (1 page, 220 bytes).
> Transcript written on x.log.
>
> Result on a 2.0.2-17:
> This is TeXk, Version 3.14159 (Web2C 7.4.5)
> %&-line parsing enabled.
> (./x.tex
> ! Undefined control sequence.
> l.2 \documentclass
> {article}
> ?
>
Could you give us a little example, how such a file could look like
you want to compile here?
> A very weird point, while tracking the bug:
> - the host is a recent woody; upgraded properly to sid
> - the first realease tested is a tetex-bin 2.0.2-17 vanilla
> (taken on a close debian mirror). The bug is shown.
> - apt-get source tetex-bin, and dpkg-buildpackage, and installing
> the 2.0.2-17 homebuilt (via dpkg -i). Same bug.
> - getting via ftp a previous release (2.0.2-16), installing with
> dpkg -i. The bug disapears.
>
Did you note, that we have changed the default latex compiler between
-16 and -17. In -16 the traditional Knuth compiler was used, in -17
we use e-TeX. I don't know what you do here. Do you use hown grown
formats to process your files or do you use normal LaTeX formats?
In the latter case I'd just ask: What don't you call latex if you
want to process LaTeX files, but I guess this is not what you want.
> - re-installing the homebuilt 2.0.2-17 via dpkg -i. The bug does
> not come back.
> - re-installing the official 2.0.2-17 via apt-get install --reinstall.
> The bug does not come back.
>
After all that operations: /usr/bin/latex is a soft link and points
to where: /usr/bin/tex or /usr/bin/etex?
What does "ls -l /var/lib/texmf/web2c/*latex*" say (assuming you want
to use latex formats).
> So there is probably on obscure link with the debian packaging system
> somewhere... Perhaps something like "works in update, but not in
> install".
>
> Moreover, this option (--parse-first-line) seems to be activated as
> a default (was not in 2.0.2-5.1, but is in 2.0.2-16 and 2.0.2-17)
> which seems weird (and is close to violating TeX's license since
> the behaviour is modified without modifying the name).
>
Sorry, I've never used that option. The only invasive influence to
the TeX compiler we did between -16 an -17 when we started calling
eTeX to process LaTeX files.
H.
--
sigmentation fault
Reply to: