Bug#244601: tetex-extra: similar but not identical error here

[Frank Küster <frank@debian.org>]

clone 244601 -1
retitle -1 fmtutil fails on {pdf}{e}tex
reassign -1 tetex-bin
submitter -1 Anthony Campbell <ac@acampbell.org.uk>
stop

Anthony Campbell <ac@acampbell.org.uk> wrote:

> Package: tetex-extra
> Version: 2.0.2a-1
> Followup-For: Bug #244601
>
>
>
> -- Package-specific info:
> Please read and follow the instructions in the first lines below
> the text: "-- Package-specific info:".
> Thank you.
> -----------------------------------------
>
> I get the same message when trying to upgrade to the current version of
> tetex-bin and tetex-extra in Sid, which I've been following for some
> time without problems.
>
>
> I've looked throught the correspondence about this bug but remain
> somewhat confused about the fix, if any. Are we suppose to purge
> tetex-bin and tetex-extra and reinstall?

No, your problem is a completely different one, although for you the
messages might look similar. I'm splitting this off as a separate bug
(Package tetex-bin).

> Error: `tex -ini  -jobname=latex -progname=latex latex.ini' failed
> Error: `etex -ini  -jobname=elatex -progname=elatex *elatex.ini' failed
> Error: `pdftex -ini  -jobname=pdflatex -progname=pdflatex pdflatex.ini' failed
> Error: `pdfetex -ini  -jobname=pdfelatex -progname=pdfelatex *pdfelatex.ini' failed
[...]
> fmtutil failed. Output has been stored in
> /tmp/tetex.postinst.XX4kfBmi
> Please include this file if you report a bug.

Do you have that file? Additionally /var/lib/texmf/web2c/tex.log would
be interesting (or only the part around the first occurence of a "!" at
the beginning of a line).

> Versions of packages tetex-extra depends on:
> ii  dpkg                          1.10.23    Package maintenance system for Deb
> ii  gsfonts                       8.14-3     Fonts for the Ghostscript interpre
> ii  tetex-base                    2.0.2a-1   Basic library files of teTeX
> pn  tetex-bin                                Not found.

This cannot be true (i.e. was not true when the error messages were
produced), because if tetex-bin would not be installed, the fmtutil
program would not be there (and therefore could not issue error
messages).

If you install tetex-bin, but the error messages remain, we also need
the output of the command (as root)

debconf-show tetex-bin

Regards, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie