Bug#198224: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000' failed.
Hi all,
this is an old bug reported against tetex-bin, which showed up when
jadetex was installed. We need some further information, see below
> From: "John F. Davis" <davis@skink.net>
> Subject: Bug#183285: jadetex: more information on jadetex install failure *** Please type your report below this line ***
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux tadpole 2.4.21-rc8 #2 Mon Jun 16 10:22:03 EDT 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages jadetex depends on:
> ii debianutils 2.5.2 Miscellaneous utilities specific t
> ii tetex-bin 2.0.2-4.1 teTeX binary files
> ii tetex-extra 2.0.2-4 extra teTeX library files
>
> -- no debconf information
>
>
> =============================================
> Here is the dump of the install: It shows me purgeing the previous install
> and the attempted reinstall. At the end, I include the jadetex.log
> from my /usr/share/texmf/web2c directory.
>
> I am trying to get jadetex so I can build the DocBook documents in the
> linux kernel directory.
>
[...]
> root# apt-get install jadetex
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Recommended packages:
> openjade1.3 openjade
> The following NEW packages will be installed:
> jadetex
> 0 packages upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
> Need to get 0B/170kB of archives.
> After unpacking 555kB of additional disk space will be used.
> Selecting previously deselected package jadetex.
> (Reading database ... 59325 files and directories currently installed.)
> Unpacking jadetex (from .../jadetex_3.13-1_all.deb) ...
> Setting up jadetex (3.13-1) ...
> mktexlsr: Updating /var/lib/texmf/ls-R...
> mktexlsr: Updating /var/spool/texmf/ls-R...
> mktexlsr: Done.
> Did't run update-fmtutil as you requested!
> Did't run update-texmf as you requested!
The last two lines show that the debconf questions regarding these two
scripts had been answered "no", which was the default in
2.0.2-4.1. Since 2.0.2-4.2 the default is yes, thus the problem won't
occur again. The debian tetex maintainers' position is that anybody who
now answers "no" should now what they are doing, and know how to handle
the problem.
Furthermore, I think Adam has made jadetex foolproof so that it will
install even if the answer was no.
However, the problem reported was not that the jadetex formats could not
be generated, but a problem with metafont. But what actually happened is
unclear. What I would like to know is the following:
- Can or could the problem be reproduced in any way? If yes, also with
current versions from unstable?
- Where there, or if reproducible, are there any files with names "mf*"
in /var/lib/texmf/web2c/, and if yes which?
- The contents of /etc/texmf/fmt.d/00tetex.cnf and
/etc/texmf/fmtutil.cnf
Without answer at least to some of these questions, we won't be able to
check whether there is really a bug in our package, or it was just some
bad accident.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: