Bug#334658: tetex-bin: updmap was run as root

[Ralf Stubner <ralf.stubner@physik.uni-erlangen.de>]

On Wed, Oct 19, 2005 at 07:31 +0200, Jean Charles Delépine wrote:
> Package: tetex-bin
> Version: 3.0-9
> Severity: normal

Thanks for reporting.

> Got #334613 bug on upgrade.
> 
> /tmp/tetex.updmap.XXQqSsSl said :
> [...]
> !!! ERROR! The map file `lm.map' has not been found at all.
> 
>     Either put this file into the right place or remove the
>     reference from the configuration file. An automatic way
>     to disable unavailable map files is to call
>       updmap-sys --syncwithtrees
> 
>     For manual editing, call
>       updmap-sys --edit
> 
> I ran updmap-sys --syncwithtrees as requeted and then apt-get -f install, 
> The tetex-bin configuration goes fine but :

I wondered why this would help at all. So I used a clean pbuilder and
did the following:

apt-get update
apt-get install tetex-base
echo "Map lm.map" > /etc/texmf/updmap.d/10local.cfg
apt-get install tetex-bin

I get the error message about "lm.map" not found. 

updmap-sys --syncwithtrees  
apt-get -f install

did indeed help, although both /etc/texmf/updmap.d/10local.cfg and
/var/lib/texmf/web2c/updmap.cfg still contain "Map lm.map". However,
updmap-sys --syncwithtrees creates a fixed
/usr/share/texmf/web2c/updmap.cfg. Normally, this is behind
/var/lib/texmf/web2c/updmap.cfg in the search path, but not for
updmap-sys, which changes some variables like this:

# kpsewhich --format="web2c files" updmap.cfg
/var/lib/texmf/web2c/updmap.cfg
# export TEXMFCONFIG=`kpsewhich -var-value TEXMFSYSCONFIG`
# export TEXMFVAR=`kpsewhich -var-value TEXMFSYSVAR`
# kpsewhich --format="web2c files" updmap.cfg
/usr/share/texmf/web2c/updmap.cfg

Of course, this does not explain why "lm.map" is mentioned in your
updmap.cfg file without being present on the system. Did you have the
lmodern package installed at some time?
 
> Warning: updmap was run as root; updmap-sys was used instead.
> If this was done by a Debian package upon installation,
> upgrade, or removal, please file a bug against that package.

Strange. This doesn't happen here. Do you have the environent variable
$SHOW_UID_WARNING set?

cheerio
ralf