Description of problem: %pre and %post scripts need to make sure that updmap.cfg is the one which is listed by 'texconfig-sys conf' on the original installation and which is marked as %config by rpm. Otherwise they create a new, independent, updmap.cfg in some directory which depends on changeable ordering in $TEXFONTMAPS variable. In other words a postinstall scriptlet should be like this: /usr/bin/texhash if [ "$1" = "1" ]; then /usr/bin/updmap-sys --cnffile /usr/share/texmf/web2c/updmap.cfg \ --quiet --nohash --enable Map=kerkis.map fi and postuninstall one if [ "$1" = "0" ]; then /usr/bin/updmap-sys --cnffile /usr/share/texmf/web2c/updmap.cfg \ --quiet --nohash --disable kerkis.map fi /usr/bin/texhash Version-Release number of selected component (if applicable): tetex-font-kerkis-2.0-9.fc5 but this equally applies to tetex-font-kerkis-2.0-9.fc4 How reproducible: always and creating updmap.sys is messing up a system as the first found updmap.sys is used so cleaning that up requires not only removing such extra configuration files and rerunnig, with a correct configuration file, updmap-sys for all extra packages with configuration written in a "wrong" places. Nasty and I do not see a good way to make that automatic.
I believe this is a bug in tetex. texconfig-sys conf specifies TEXMFSYSCONFIG=/usr/share/texmf-config, and that is where updmap.cfg should be located. The marking of /usr/share/texmf/web2c/updmap.cfg as config is an rpm specific thing which should also be changed. I opened a bug against tetex (bug #172507) and will wait to see the reaction before closing this.
Given the discussion in bug #172507, it looks like an interim solution could be to use a run-time configuration file. It seems also safe both for systems which do and do not have tetex-font-cm-lgc installed. I will update the spec file as suggested in comment #2 of bug #172491. Thanks