Bug#249597: texmf: Leaves spurious tempfiles around

[Hilmar Preusse <hille42@web.de>]

On 25.05.04 Frank Küster (frank@debian.org) wrote:
> Frank Küster <frank@debian.org> wrote:

Hi Frank,

> > It's a little harder with the fmtutil call: Currently, we grep
> > through the tempfile for the "I'm stymied" message,
> 
> This does not make sense AFAIS, because fmtutil will grep for errors
> itself, and exit 1 if it encounters one. 
> 
> I have just committed a change that does essentially the following:
> 
> tempfile=`mktemp -p $TMPDIR tetex.postinst.XXXXXXXX`
> echo "Running initex. This may take some time. ..."
> if $TEXINIT_P > $tempfile; then
>   rm -f $tempfile
> else
>   echo
>   echo "fmtutil failed. Output has been stored in"
>   echo "$tempfile"
>   echo "Please include this file if you report a bug."
>   exit 1
> fi
> 
Before we were calling fmtutil --all twice. I guess this was done
with intention. Shouldn't we keep that? Or do you think, that this is
a bug in fmtutil, like mentioned in your second mail:
"If it turns out that there can be "I'm stymied" messages without
fmtutil giving an error, this should be fixed in fmtutil, not in our
postinst."
AFAICS fmtutil checks after building the formats, if the format exist
but not, if they match to the compiler.

drachi:~# grep sty fmtutil
drachi:~#

fmtutil:

  if test -f $fmtfile; then
    grep '^! ' $format.log >/dev/null 2>&1 &&
      log_failure "\$engine -ini $tcxflag $jobswitch $prgswitch $texargs' possibly failed."
  else
    log_failure "\$engine -ini $tcxflag $jobswitch $prgswitch $texargs' failed" 
  fi

H. 
-- 
sigmentation fault