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

Bug#487630: SUCCESS after removal of 00tetex.cnf



Hilmar Preusse <hille42@web.de> wrote:

> Well, the postinst- and preinst scripts of teTeX in Debian are/were
> rather a nightmare regarding "which files have to be
> removed/fixed/changed to resurrect mistakes made before". You may
> have a look at them just for fun. 

A strange kind of fun, though...

> Your 00tetex.cnf does not have the magic 
> "# -_- DebPkgProvidedMaps -_-" snipped, hence is it read when
> creating the fmtutil.cnf.
>
> To get a fix I suggest that the preinst script of an important
> package (tex-common ?) greps for that snippet through all files in
> /etc/texmf/fmt.d/ and renames all files, which do not have it (e.g.
> append the extension "unused") and inform the end user about it.

I fear this can't be done, because that means that any user-generated
file will be disabled. This is against the spirit and wording of the
policy, and can only be justified in really bad cases (like our
resurrecting modes.mf). And in particular it is against the basic idea
behind introducing the DebPkgProvidedMaps magic: It was invented in
order to distinguish between Debian-provided parts (which may face the
"race condition" problems during configuration) and locally installed
stuff.

> Any further ideas?

One and a half. 

Half: Looking for specific files (here: 00tetex.cnf) without
DebPkgProvidedMaps. This would, however, create a danger of getting back
to maintainer scripts which give the reader exactly the same kind of
"fun" we had in teTeX.

One: We already do that.

$ egrep -v '^$|^#' texlive-base/debian/texlive-common.postinst.pre 
for i in updmap.d/10tetex-base.cfg fmt.d/01tetex.cnf language.d/00tetex.cnf language.d/10tetex.cnf ; do
	if [ -r /etc/texmf/$i ] ; then
		mv /etc/texmf/$i /etc/texmf/$i.obsolete
		echo "Obsolete config file /etc/texmf/$i has been renamed" >&2
		echo "as /etc/texmf/$i.obsolete." >&2
	fi
done

In other words: We move fmt.d/01tetex.cnf to
fmt.d/01tetex.cnf.obsolete. Either this is the worng[1] filename, or
rather we had both...

Regards, Frank




[1] that's just a typo. But it reminded me of the German "Im Usenet
schreibt man flasch immer falcsh"



-- 
Frank Küster
Debian Developer (TeXLive)
ADFC Miltenberg
B90/Grüne KV Miltenberg



Reply to: