Bug#379089: marked as done (tex-common: unclear wording of debconf messages, assumes wrongly mktex.cnf has been created by a knowing admin)
Your message dated Wed, 16 Aug 2006 08:17:52 -0700
with message-id <E1GDN9Ufirstname.lastname@example.org>
and subject line Bug#379089: fixed in tex-common 0.27
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 ---
- To: Debian Bug Tracking System <email@example.com>
- Subject: tex-common: unclear wording of debconf messages, assumes wrongly mktex.cnf has been created by a knowing admin
- From: Frank Küster <firstname.lastname@example.org>
- Date: Fri, 21 Jul 2006 09:15:47 +0200
- Message-id: <email@example.com>
Manoj Srivastava <firstname.lastname@example.org> wrote:
> Today, when upgrading my unstable box, I got a debconf message
> from the package tex-common, to wit:
> “The mechanism of TeX font caching has changed, requiring the
> installation of /usr/share/texmf/web2c/mktex.cnf. On your
> system, /etc/texmf/web2c/mktex.cnf exists with possible local
> changes, and makes the new file invisible to TeX. Font
> caching might not work until the setting of MT_FEATURES has
> been transferred to your configuration file.”
> What does this imply? Why are configuration files (I am
> assuming that something called mktex.cnf is actually a configuration
> file) being installed in /usr/share/?
Because of this paragraph from the TeX Policy Draft:
,---- 4.1 Configuration files
| In a TeX system, in principle every TeX input file can be changed to
| change the behavior of the system, and thus be regarded as a
| configuration file. To prevent inflation of configuration files,
| packages should not install any TeX input files as conffiles or
| configuration files. Instead, they should create an empty directory
| below /etc/texmf/tex and advice users which files are likely places
| for configuration. It is up to the local admin or individual user to
| place changed copies in TEXMFSYSCONFIG or TEXMFCONFIG, respectively.
> What exactly is the usewr
> supposed to do, anyway? If nothing, why is there a debconf notice?
We expected that /etc/texmf/web2c/mktex.cnf will never exist on a system
unless the local admin has deliberately created it. So this debconf
message is targetted at people who already now how to change the TeX
system by placing files in appropriate directories below /etc/texmf, and
thus also how to deal with the situation.
Well, it seems there are other reasons why this file can exist. Without
exactly looking at the code, one place that we forgot comes to my mind:
The texconfig-sys utility. If this is used to change the system
configuration, it will create files in TEXMFSYSCONFIG.
So far for the general reasons, so far no conclusion.
What's the content of the file on your system? Do you remember having
made any changes to the TeX system, maybe with the texconfig utility?
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is fixed in the latest version of
tex-common, which is due to be installed in the Debian FTP archive:
A summary of the changes between this version and the previous one is
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to email@example.com,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Frank KÃ¼ster <firstname.lastname@example.org> (supplier of updated tex-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing email@example.com)
-----BEGIN PGP SIGNED MESSAGE-----
Date: Wed, 16 Aug 2006 16:58:01 +0200
Architecture: source all
Maintainer: Debian TeX maintainers <firstname.lastname@example.org>
Changed-By: Frank KÃ¼ster <email@example.com>
tex-common - Common infrastructure for using and building TeX in Debian
Closes: 379089 379234 382967
tex-common (0.27) unstable; urgency=medim
* Policy Change: Treat configuration files properly as Debian Policy
mandates. The only TeX-specific addition is that we remind
maintainers to only treat files for site-wide changes as configuration
files, not files intended to change the typeset output on a
per-document or per-project basis. Consequently, mktex.cnf is now
installed as /etc/texmf/web2c/mktex.cnf. Thanks to Manoj Srivastava!
This closes: #379089, a RC bug, hence the medium urgency [frank]
* Really install NEWS.Debian about the font cache changes in the last
* Update changelog for 0.16. We forgot to close two bugs. [hilmar-guest]
* Debconf Translations: [frank]
- Update Dutch translation, thanks to Vincent Zweije
<firstname.lastname@example.org> (closes: #379234)
- Update Spanish translation, thanks to Javier FernÃ¡ndez-Sanguino PeÃ±a
<email@example.com> (closes: #382967)
a5a545252d0004765f85ce3923ed1bad 756 tex optional tex-common_0.27.dsc
45d7af8cbca0acce3fcd76e47c60f714 304342 tex optional tex-common_0.27.tar.gz
8ba0bb37956a85a253ab58dc859d8509 287152 tex optional tex-common_0.27_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
-----END PGP SIGNATURE-----
--- End Message ---