Bug#263296: tetex-bin 2.0.2-17 broke "tex --parse-first-line"
Le Tue, Aug 03, 2004 at 10:56:38PM +0200, Hilmar Preusse:
> > 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?
As stated in the previous answer: any LaTeX document with the
line "%&latex" prepended.
> 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.
That is of concern if I use latex as a command. I guess it is not if I
use tex... The points is that this special use of tex (as stated by the
upstream maintainer) is in a script (makempx) that is called from within
mpost. makempx can be used on plain-TeX or on LaTeX documents. To ease
the use of the script, they do choose the real format with the first
line of the document which is supposed to contain the special comment
giving the name of the format.
> > - 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).
latex is indeed a soft link on etex now (I don't know how it was while
the bug was present), but the problem is with tex, not with latex. And
the formats seems to be ok:
madflo@rei:~$ ls -la /usr/bin/latex
lrwxrwxrwx 1 root root 4 Aug 3 19:40 /usr/bin/latex -> etex
madflo@rei:~$ which etex
/usr/bin/etex
madflo@rei:~$ ls -l /var/lib/texmf/web2c/*latex*
-rw-r--r-- 1 root root 1648737 Aug 3 19:40 /var/lib/texmf/web2c/elatex.efmt
-rw-r--r-- 1 root root 13592 Aug 3 19:40 /var/lib/texmf/web2c/elatex.log
-rw-r--r-- 1 root root 1648681 Aug 3 19:40 /var/lib/texmf/web2c/latex.efmt
-rw-r--r-- 1 root root 1645359 Aug 3 19:18 /var/lib/texmf/web2c/latex.fmt
-rw-r--r-- 1 root root 13587 Aug 3 19:40 /var/lib/texmf/web2c/latex.log
-rw-r--r-- 1 root root 1657605 Aug 3 19:40 /var/lib/texmf/web2c/pdfelatex.efmt
-rw-r--r-- 1 root root 13615 Aug 3 19:40 /var/lib/texmf/web2c/pdfelatex.log
-rw-r--r-- 1 root root 1657596 Aug 3 19:40 /var/lib/texmf/web2c/pdflatex.efmt
-rw-r--r-- 1 root root 1654290 Aug 3 19:18 /var/lib/texmf/web2c/pdflatex.fmt
-rw-r--r-- 1 root root 13610 Aug 3 19:40 /var/lib/texmf/web2c/pdflatex.log
But, that is the state as when the bug disapeared after the
downgrade-upgrade process. I cannot give you back informations about how
it was while there was the problem...
Benjamin.
Reply to: