Bug#65432: tetex-bin: kpsewhich cannot find file fmtutil.cnf
If you even not have texhash this means that your tetex-bin
installtion is completely broken. Please purge and reinstall.
OK, done ... and it does not help. `kpsewhich' still cannot find
`fmtutil.cnf':
# dpkg --purge tetex-bin
(Reading database ... 87898 files and directories currently installed.)
Removing tetex-bin ...
Purging configuration files for tetex-bin ...
# apt-get install tetex-bin
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
tetex-bin
0 packages upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0B/2656kB of archives. After unpacking 6040kB will be used.
Selecting previously deselected package tetex-bin.
(Reading database ... 87894 files and directories currently installed.)
Unpacking tetex-bin (from .../tetex-bin_1.0.6-7_i386.deb) ...
checking for old tex packages ... none.
Setting up tetex-bin (1.0.6-7) ...
mktexlsr: Done.
Error: kpsewhich cannot find file fmtutil.cnf
dpkg: error processing tetex-bin (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
tetex-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
You wrote:
Sorry, but your installation seams to broken. And this is special to
your situation.
If this is the case, apt-get should report better error messages
.... a different kind of bug report :-)
However, if it is the case, I doubt it will be special only to me,
since this installation of Debian is a straightforward installation of
slink followed, over time, with dist-upgrades to frozen. That is is
say, I used a CD with `slink and a half' on it, followed by some
custom burned CDs with unstable from mid-January followed by
apt-get dist-upgrade
which consistently reports no problems.
(The current installation is rather recent. I made it at the end of
April, when I suffered a catastrophic hard disk failure and had to
install a new drive. I had not backed up system files, only files of
my own, so the Debian files are from slink upgraded through unstable
to frozen.)
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
Reply to: