[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420393: marked as done (tetex-bin: Configuration file handling is fragile)

Your message dated Wed, 25 Apr 2007 09:35:48 +0200
with message-id <200704250936.01662.elendil@planet.nl>
and subject line Bug#420393: tetex-bin: Configuration file handling is fragile
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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 

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 

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.


[1] I was using 'dpkg -i' to install the Etch version of tetex packages 
while investigating #420390.

Attachment: pgpwcX2vqEGNu.pgp
Description: PGP signature

--- End Message ---
--- Begin Message ---
On Monday 23 April 2007 20:18, you wrote:
> AFAIK tetex-bin had this file even in sarge, but I'm not sure whether
> it was ucf-managed back then.  Are you sure you had purged tetex-bin
> before that, or was it maybe still in state "rc"?

I am fairly sure I did have it purged, but I wouldn't swear on it.
I cannot reproduce the issue anymore either, so either you are right and I 
did not purge it, or it is some other weird corner case.

Let's close this one, but I'll keep an eye out for repetitions.

Attachment: pgpfSoh7FNJ4E.pgp
Description: PGP signature

--- End Message ---

Reply to: