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

Bug#412242: tetex-bin: mktexpk places some fonts in the current directory



reassign 412242 texlive-base-bin
merge 412242 412653
stop

On 24.02.07 Sergei Ivanov (svivanov@pdmi.ras.ru) wrote:

Hi Sergei,

http://bugs.debian.org/412242

> Package: tetex-bin
> Version: 3.0-29
> Severity: normal
> 
> On my system, the command
>   mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 lhr10
> places the resulting file lhr10.720pk in the current working directory.
> (The font lhr10 is a cyrillic version of cmr10, I think it belongs
> to tetex-extra.)
> 
> At the same time, the same command with cmr10 in place of lhr10
> places the result under ~/.texmf-var.
> 
> The difference between lhr10 and cmr10 is that I have lhr10.tfm
> and some other lh* files under /var/lib/texmf (they were probably 
> created by fmtutil since I use custom formats with these fonts).
> "rm -rf /var/lib/texmf/fonts" fixes the problem.
> 
> I tried to debug it and found that one of the scripts (maketexnam)
> finds lhr10.tfm under /var/lib/texmf but fails to recognize that
> /var/lib/texmf is a "system" tree.
> 
Frank analyszed that bug and found out that the problem only occurs
if TEXMFSYSVAR is nor part of SYSTEXMF. Actually (TL 2007) this is
not the case any more and I couldn't reproduce your bug any more.

hille@kloetzer:~ $ mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 lhr10
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour;
mag:=1+120/600; nonstopmode; input lhr10
This is METAFONT, Version 2.71828 (Web2C 7.5.6)

(/home/hille/.texmf-var/fonts/source/lh/lh-lcy/lhr10.mf

<snip>

Font metrics written on lhr10.tfm.
Output written on lhr10.720gf (210 characters, 49436 bytes).
Transcript written on lhr10.log.
mktexpk:
/home/hille/.texmf-var/fonts/pk/ljfour/lh/lh-lcy/lhr10.720pk:
successfully generated.
/home/hille/.texmf-var/fonts/pk/ljfour/lh/lh-lcy/lhr10.720pk
hille@kloetzer:~ $ 

Can you? If not, is it OK to close that bug?

Thanks,
  Hilmar
-- 
sigmentation fault



Reply to: