Bug#113899: jadetex: jadetex broken installation on woody

[Olaf Weber <olaf@infovore.xs4all.nl>]

Christoph Martin writes:
> Adam Di Carlo writes:
>> Christoph Martin <martin@uni-mainz.de> writes:

>>> I can't reproduce this problem. Can anybody else? If not, I would like
>>> to close it, as the problem apparently vanished when the submitter
>>> purged and reinstalled.

>> Don't you think it's a problem that people commonly have problems with
>> tetex upgrades, especially upgrades across long time periods?

>> Shouldn't you leave this bug open until the *source* of those problems
>> are fixed?

> Do you know the *source* of the problem? If I can't reproduce it, how
> should I find and fix it?

This is the awkward category of bugs where you know there is a problem
but didn't get enough data to determine what it is.

What to do next time:

Find out which commands fmtutil runs to generate the format, then run
them by hand, adding options to crank up the logging level.  In
particular, add '-kpathsea-debug=-1' to TeX's command line to get a
low-level view of which files are being opened, including the full
path names.  (From web2c 7.3.6 based TeX onward, you can also specify
'-recorder' to get a file <jobname>.fls containing a more readable
list of files opened.)  And make sure you get this output & the log
files ASAP, before the problem vanishes into thin air again.

If the problematic file is ecrm1000.tfm, finding _all_ files with that
name and getting copies (or at least 'file' run on them) is also a
good idea.

-- 
Olaf Weber

Do not meddle in the affairs of sysadmins,
        for they are quick to anger and have no need for subtlety.