Ralf Stubner <[EMAIL PROTECTED]> wrote:
> In the case where this started, the user would have been back at 'square
> one', since updmap-sys would again try to use the still incorrect
> /var/lib/texmf/web2c/updmap.cfg and again suggest 'updmap-sys
> --syncwithtrees' or 'updmap-sys --edit'.
I'm not sure I understand whay you mean. I see two cases:
- users who encountered #334658 and did not run
'updmap-sys --syncwithtrees'
-> for these users, the fix I proposed in #334658 must work (I
tested it)
- users who encountered #334658 and did run 'updmap-sys --syncwithtrees'
-> if they blindly follow the same procedure without the rest,
they will install lmodern 0.92-9, which will run:
update-updmap -> generates a correct
/var/lib/texmf/web2c/updmap.cfg
updmap-sys -> uses the bad updmap.cfg under TEXMFMAIN
Doesn't work. They have to remove the bad updmap.cfg from
TEXMFMAIN first. Is that what you meant?
But as far as tetex-bin is concerned, if the bad updmap.cfg is removed
before the updmap-sys call in tetex-bin.postinst, things should be all
right, no?
[ update-updmap will generate /var/lib/texmf/web2c/updmap.cfg even if
updmap.cfg exists under TEXMFMAIN:
SYSWIDE_VARD=/var/lib/texmf/web2c
DEFAULT_OUTPUTFILE_BASENAME=updmap.cfg
SYSWIDE_DEFAULT_OUTPUTFILE="$SYSWIDE_VARD/$DEFAULT_OUTPUTFILE_BASENAME"
No kpsewhich call here. ]
--
Florent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
