Paul Menzel <[EMAIL PROTECTED]> wrote: > I finally found [1] and the /usr/share/texmf-tetex (or texlive – I do > not remember and I do not have access to the computer now) was not in my > paths either.
And you upgraded from an old machine to unstable, right? We have added the texlive path to TEXMFDIST during the sarge->etch upgrade, and AFAIR we had a check for that (which failed with a user-friendly error message). Now in the etch->lenny upgrade, we remove texmf-tetex and only keep texmf-texlive. This probably means that if someone skips a release (which is generally not supported), they should manually remove tetex before upgrading tex-common (the package wich contains the TEXMFDIST setting). The question is whether we want to care for this problem, or simply say "You have been warnded"? > Unfortunately there were no information about what tools > to use, to modify the paths. Or rather, you did not find them. I'm not sure in which state your system was. But it seems you already had upgraded tex-common, you should have found /usr/share/doc/tex-common/TeX-on-Debian*. All versions have a table of contents, and in the second chapter, "Changing your configuration, file placement", the first section is "Available TEXMF trees for users and system administrators" which contains the necessary information or links to them. Any ideas how we could have helped you find that info? > Therefore I manually edited the config file > by adding the path to dvips35.map to a variable in the beginning. If you've added /etc/texmf/texmf.d/05TeXmf.cnf and run update-texmf, that was right. After removing all traces of teTeX, you can now remove the texmf-tetex part of the path again. Regards, Frank -- Frank Küster Debian Developer (teTeX/TeXLive)
