Comment 25 for bug 24478

Revision history for this message
In , Frank Küster (frank-debian) wrote : Re: Bug#335303: tetex-bin: failed to install: updmap error

Sebastien Helleu <email address hidden> wrote:

> On Sun, Oct 23, 2005 at 02:14:17PM +0200, Florent Rougon wrote:
>>
>> # mv 00updmap.cfg.dpkg-dist 00updmap.cfg
>> # mv 20tetex-extra.cfg.dpkg-new 20tetex-extra.cfg
>> # dpkg --configure -a
>>
>> --
>> Florent
>
> Done, still same problem..
>
> Here's output of dpkg and content of new resulting file in /tmp:
>
> $ dpkg --configure -a
> Setting up tetex-bin (3.0-10.1) ...
> Running fmtutil-sys. This may take some time. ...
> Running updmap-sys. This may take some time. ...
> updmap failed. Output has been stored in
> /tmp/tetex.updmap.XX7jegVt
[...]
> updmap-sys: Scanning for LW35 support files
>
> !!! ERROR: The right location for map files has been
> changed for this release and the map file `dvips35.map' has
> not been found in the right location, but in the obsolete
> location
> /usr/share/texmf/dvips/config/dvips35.map
> instead.

There is a compatibility symlink from /usr/share/texmf/dvips/config to
/etc/texmf/dvips, this is intended. However, there should be no file
"dvips35.map" in that directory. The file should be found as

/usr/share/texmf/fonts/map/dvips/tetex/dvips35.map

*first*, i.e. this file should be used even if a copy exists in
/etc/texmf/dvips..

The file dvips35.map from current tetex-base is in fact stored in
/etc/texmf/map/dvips/tetex/dvips35.map and made available with a symlink

/usr/share/texmf/fonts/map/dvips -> /etc/texmf/map/dvips

This symlink exists on your system, as you have shown earlier; but I
don't know whether the file is there. If it is there, the question is
whether it does not take precedence over the one in /etc/texmf/dvips,
and after all why that file exists in /etc/texmf/dvips, anyway.

I think the answer to the last question might be that it once was there
(in a version in sarge/sid when sarge was still testing), and has been
forgotten from the list in README.Debian - in fact it is listed in the
remove-oldmaps script.

The answer to the first question - why is the wrong file found - is
unclear to me. Sebastien, what is the output of the following commands:

kpsewhich --format=map dvips35.map
kpsewhere --format=map dvips35.map
kpsewhere dvips35.map
kpsewhich --show-path map

grep ^TEXFONTMAPS /etc/texmf/texmf.cnf
grep ^TEXFONTMAPS /etc/texmf/texmf.d/*

Thanks in advance, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer