Changes

The Debian tetex-3.0 package (and probably the vanilla tetex-3.0) in combination with <tt>texexec</tt> puts user-generated If you have format files in <tt>~/.texmf-var/web2c/<i>engine</i></tt> where <i>engine</i> is typically <tt>pdfetex</tt>. (If you don't have such a directory, and you are using then these will shadow the default tetex configuration, tell ones installed by the mailing list so that this installation information can be corrected!)context package. So you need delete them.

The default To find them, use <tt>kpsewhich cont-en.fmt</tt> (and similarly for the other formats). Run the <tt>tetexkpsewhich</tt> setup doesnfrom a 't know about such locations typical' directory (it doesn't know what it shoulde.g. your home directory), and it instead knows about other locations rather than from <tt>~/.texmf-var/web2c/pdfetex/</tt> (adjust for your engine), otherwise it knows what it shouldn't). Here is how to fix both problemswill find the newly created formats before any others.

=== Older context formats === There may be older context formats lying around, and the path searching code may find these older ones instead of the new ones lovingy made by <tt>texexec</tt>. ==== Deleting the older context formats ==== So you need delete the older ones. But where are they? When I ran <tt>texexec</tt>, it made <tt>cont-en.fmt</tt>, <tt>cont-nl.fmt</tt>, and <tt>mptopdf.fmt</tt> in <tt>~/.texmf-var/web2c/pdfetex/</tt> and they were shadowed by the older versions: <tt>~/.texmf-var/web2c/cont-en.fmt</tt>, etc. So I deleted the older ones.  If you cannot find them, use <tt>kpsewhich cont-en.fmt</tt> (and similarly for the other formats). Run the <tt>kpsewhich</tt> from a 'typical' directory (e.g. your home directory), rather than from <tt>~/.texmf-var/web2c/pdfetex/</tt> (adjust for your engine), otherwise it will find the newly created formats before any others.  ==== Stopping fmtutil from making have context-related formats ==== But how did the older ones get there? <tt>fmtutil</tt> And will it happen again? Yes, though perhaps rarely (the most frustrating kind of bug). At the next upgrade of <tt>tetex</tt>, which happens frequenty on Debian, the installation scripts will rerun <tt>fmtutil</tt> as root. That probably won't cause you trouble because the formats generated will go installed in a system-wide format directory (e.g. in that precedes <tt>/varusr/libshare/texmf/web2c/</tt>), and your new ones will override them once you finish these steps.  However, if you, as an ordinary user, run <tt>texconfig</tt>, say to change your own default paper size from <tt>letter</tt> to <tt>a4</tt>, then <tt>tetex</tt> they will regenerate all formats for you and put them in your format location <tt>~/.texmf-var/web2c/</tt> (without using shadow the engine subdirectory). And you're in ones installed by the soup again. So stop <tt>fmtutil</tt> from making any context-related formatspackage, and let <tt>texexec</tt> handle it. On standard <tt>tetex</tt> setups, you'd edit <tt>fmtutil.cnf</tt> (probaby in <tt>/var/lib/texmf/web2c/</tt>), but on Debian systems, that file is autogenerated from configlets (tiny pieces of will get a config file) living in <tt>/etc/texmf/fmt.d/</tt>.  As <tt>root</tt>:  emacs -nw /etc/texmf/fmt.d/01tetex.cnf (or choose your favorite editor). Comment out clash (with a <tt>#!</tt>) the lines for <tt>mptopdf</tt>, <tt>metafun</tt>, <tt>cont-en</tt>, and any other <tt>cont-*</tt> formats not already commented out. Now generate a new system-wide configuration file:  update-fmtutil === Finding the new formats === The path searching code format files will not find be the newer formats because ones installed by the code doesn't search subdirectories of <tt>web2c/</tt>. The simple fixpackage, telling it to search all subdirectories, does not work: Context may use several different engines, e.g. <tt>pdfetex</tt> or <tt>xetex</tt>, each with a set of formats, and you want <tt>texexec</tt> to find the correct set. If it searches all subdirectories, it but later versions will use the first set that it happens to run across, which may not match the engine that you use. Instead the searches should look be read in the subdirectory chosen according to the <i>engine</i>).  To specify this kind of search, So you'd normally edit <tt>texmf.cnf</tt> directly, but Debian uses configlets for it. So edit (still as root) the <tt>TEXFORMATS</tt> line in <tt>/etc/texmf/texmf.d/45TeXinputs.cnf</tt> need to include this magic:  TEXFORMATS = .;$TEXMF/web2c/{$engine,} It says to look first in move the <i>engine</i> subdirectory, then in the <tt>web2c</tt> directory itself. Now generate a new <tt>texmf.cnf</tt> configuration file (still as root):  update-texmf That step generates a new <tt>/etc/texmf/texmf.cnf</tt>, which Debian symlinks from its standard tetex location <tt>/usr/share/texmf/web2c/texmf.cnf</tt>. With luck, you are done. In shadowing context installations out of the next section you will check whether everything is working by running <tt>texexec --version</tt> (as yourself, not as root!)way.