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

Bug#478992: update-texmf: Basic configuration file /etc/texmf/texmf.d/05TeXMF.cnf missing.



Hallo A.,

A. Costa schrieb am Sun 04. May, 01:16 (-0400):
> On Sat, 3 May 2008 14:21:46 +0200
> Jörg Sommer <joerg@alea.gnuu.de> wrote:
> 
> > Frank Küster schrieb am Sat 03. May, 11:47 (+0200):
> > > "A. Costa" <agcosta@gis.net> wrote:
> > > 
> > > > It looks like 'tetex-bin' is missing some files, or it used to
> > > > have them and they're now in some other package.  What package
> > > > has those config files?
> > > 
> > > tex-common, in etch, lenny, sid. The problem with --force-confmiss
> > > is that those files are under ucf control, not dpkg control, and ucf
> > > doesn't understand --force-confmiss. 
> > 
> > Simply do
> >   UCF_FORCE_CONFFMISS=yes dpkg-reconfigure tex-common
> 
> Thanks, I got...
> 
> 	% UCF_FORCE_CONFFMISS=yes dpkg-reconfigure tex-common ; echo $?
> 	/usr/sbin/dpkg-reconfigure: tex-common is broken or not fully installed
> 	1

Sorry, I missed your installation didn't succeed.

> ...then tried that variable with 'dpkg', and (for some reason) it worked:
> 
> 	% UCF_FORCE_CONFFMISS=yes dpkg -i --force-confmiss /var/cache/apt/archives/tex-common_1.11_all.deb

Yes, this was the right thing to do.

> 	(Reading database ... 234065 files and directories currently installed.)
> 	Preparing to replace tex-common 1.11 (using .../tex-common_1.11_all.deb) ...
> 	Ignoring nonregistered document `debian-tex-policy'
> 	Ignoring nonregistered document `tex-on-debian'
> 	Unpacking replacement tex-common ...
> 	Setting up tex-common (1.11) ...
> 
> 	Recreating deleted config file /etc/texmf/texmf.d/05TeXMF.cnf with new version, as asked
> 
> 	Recreating deleted config file /etc/texmf/texmf.d/15Plain.cnf with new version, as asked
> 

> But does this constitute an actual bug in any of the current software?
> From what Frank Kuster said, it sounds like my system's odd behavior
> might have been caused by many things

Yes, was an odd behaviour of the system somewhere in the past and now,
from the package point of view it looks like the admin decided to remove
the files. That's his choice, but he must expect that things break. The
problem here is, you didn't made the decision. There was any corruption
of the system.

So, I would close this report, because it is not a bug in the package.
The system was misconfigured and the Policy force to don't change user
configuration. And it's allowed that misconfigured software breaks.

> For diagnostics, it might be nice to have some util like 'dlocate' that
> worked for config files,

This is difficult. Many packages do not announce their ownership
anywhere. They drop the files in /etc and go away.

Regards, Jörg.
-- 
A red sign on the door of a physics professor: 'If this sign is blue,
you're going too fast.'

Attachment: signature.asc
Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP


Reply to: