Bug#233886: tetex-base upgrade from woody pretend I have modified /etc/texmf/mktex.cnf

[Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp>]

From: Bill Allombert <ballombe@debian.org>
Subject: Bug#233886: tetex-base upgrade from woody pretend I have modified /etc/texmf/mktex.cnf
Date: Fri, 20 Feb 2004 16:59:33 +0100

> Hello TeTeX maintainers,

Hi,

> When doing a woody to sid upgrade from a clean woody install,
> dpkg tell me I have modified /etc/texmf/mktex.cnf
> This is simply not true and confusing.

In a sense, it is true.  It was moved from tetex-bin to
tetex-base at upgrading tetex 1.0 (woody) to 2.0 (testing) 
so dpkg would behave that way.

> The same happen for
> /etc/texmf/texmf.d/95NonPath.cnf 
> /etc/texmf/texmf.d/05TeXMF.cnf
> /etc/texmf/texmf.d/45TeXinputs.cnf
> /etc/texmf/texmf.d/75DviPS.cnf
> /etc/texmf/texmf.d/85Misc.cnf

These were renamed *.cnf at some time after woody and so
if there was old 05TeXMF then we renamed it as 05TeXMF.cnf
(because we should preserve your modifications) but again
dpkg would behave in the same way.

> /etc/texmf/dvips/config.ams
> /etc/texmf/dvips/config.cm
> /etc/texmf/dvips/config.amz
> /etc/texmf/dvips/config.cmz
> /etc/texmf/dvips/bsr-interpolated.map
> /etc/texmf/dvips/bsr.map

These were moved from tetex-base to tetex-extra because
they were files for fonts in tetex-extra and dpkg would 
behave in the same way.

I guess this is not a bug but your report is very useful 
for us because we can recognize what configuration files 
have changed their status between woody and sarge.

Thanks for your interest in tetex packages.

Regards,		    2004-2-21(Sat)

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda@debian.org>
 Department of Math., Univ. of Tokushima