Bug#200902: tetex-bin: errors on upgrade
On 16.07.03 Atsuhito Kohda (kohda@pm.tokushima-u.ac.jp) wrote:
> On xx.xx.xx Hilmar Preusse wrote:
> > On 11.07.03 Ross Boylan (RossBoylan@stanfordalumni.org) wrote:
> >
> > > 1) The log of installation reports
> > > Installing new version of config file /etc/texmf/texmf.d/95NonPath.cnf
> > > ...
> > > Regenerating /var/lib/texmf/web2c/updmap.cfg ... done
> > > Running initex. This may take some time. ...
> > > Error: `tex -ini -jobname=jadetex -progname=jadetex &latex
> > > jadetex.ini' failed
> > > Error: `pdftex -ini -jobname=pdfjadetex -progname=pdfjadetex
> > > &pdflatex pdfjadetex.ini' failed
> > >
> > I think, I've seen that bug already ones. I've not yet investigated.
>
> This is very old bug(?) but we provided a workaround as
>
Well, I should remove closed bugs not only from my web cache, but
from my brain cache too...
> From: Ross Boylan <RossBoylan@stanfordalumni.org>
> Subject: Bug#200902: tetex-bin: errors on upgrade
> Date: Fri, 11 Jul 2003 11:47:45 -0700
>
> > This is a summary of all `failed' messages and warnings:
> > `tex -ini -jobname=jadetex -progname=jadetex &latex jadetex.ini'
> > failed
> > `pdftex -ini -jobname=pdfjadetex -progname=pdfjadetex &pdflatex
> > pdfjadetex.ini' failed
> > #####
> > Failed to generate some FMT so try once again!
> > fmtutil: /usr/share/texmf/web2c/lambda.oft installed.
> > fmtutil: /usr/share/texmf/web2c/omega.oft installed.
> > fmtutil: /usr/share/texmf/web2c/amstex.fmt installed.
> > fmtutil: /usr/share/texmf/web2c/jadetex.fmt installed.
> > fmtutil: /usr/share/texmf/web2c/latex.fmt installed.
>
> that is, if generating jadetex.fmt we will run initex once again
> and it will be generated as the above shows.
>
Well, I could see the success-message for jadetex and pdfjadetex in
the log-files he posted. So, the workaround to call fmtutil --all
twice should be sufficient. #197913 and #198224 seem to be something
different.
Unfortunately this was not visible in hier first posting. I propose
too, to close that bug.
H.
--
sigmentation fault
Reply to: