Package: tetex-bin
Version: 3.0-30
Filing this against tetex-bin because that is where I observed the issue,
but I suspect it is valid in general for tetex/texlive configuration file
handling.
Over the past week I've learned that local admins are allowed to remove
TeX-related configuration files in /etc/texmf/ and that therefore tetex
and texlive packages do not install "missing" configuration files on
upgrades.
It appears that this mechanism is somewhat fragile if there are errors
when a package is first installed. Note that in this case it was a
dependency issue for the tetex package itself that caused it to remain
unconfigured, but the installation could have been broken of for any
number of reasons completely unrelated to tetex that would have resulted
in the package being left in basically the same state.
In this case, on a *new* installation of tetex-bin [1], the package
initially failed to configure because libkpathsea4 was not installed:
dpkg: dependency problems prevent configuration of tetex-bin:
tetex-bin depends on libkpathsea4; however:
Package libkpathsea4 is not installed.
dpkg: error processing tetex-bin (--install):
dependency problems - leaving unconfigured
When I corrected this by installing libkpathsea, I noticed this message:
Setting up tetex-bin (3.0-30) ...
Not replacing deleted config file /etc/texmf/fmt.d/01tetex.cnf
Apparently the configuration script decided that this was an upgrade
instead of a new install, which is not correct. I installed tetex-bin
from scratch, so the config file _should_ have been installed, even if
configuring the package failed at first.
Cheers,
FJP
[1] I was using 'dpkg -i' to install the Etch version of tetex packages
while investigating #420390.
Attachment:
pgpmUOSZDIi1U.pgp
Description: PGP signature