Description of problem: diff -u updmap.cfg.rpmsave updmap.cfg after recent upgrade ... -Map euler.map +Map ... Version-Release number of selected component (if applicable): texlive-amsfonts-svn29208.3.04-0.1.fc19.noarch How reproducible: always Steps to Reproduce: 1. upgrade to recent package version Actual results: crippled euler map entry Expected results: dull euler map entry Additional info: caused by additional spaces in postinstall and postuninstall scriptlets: % rpm -q --scripts texlive-amsfonts-svn29208.3.04-0.1.fc19.noarch postinstall scriptlet (using /bin/sh): ... /usr/bin/updmap-sys --quiet --enable MixedMap=cyrillic.map > /dev/null 2>&1 /usr/bin/updmap-sys --quiet --enable Map= euler.map > /dev/null 2>&1 ^^^^^ here ... postuninstall scriptlet (using /bin/sh): ... /usr/bin/updmap-sys --disable MixedMap=cyrillic.map > /dev/null 2>&1 /usr/bin/updmap-sys --disable Map= euler.map > /dev/null 2>&1 ^^^^^ and here ...
I see this too, please fix. The error messages that come out of pdflatex are things like kpathsea: Running mktexpk --mfmode .... eufm10 mktexpk: don't know how to create bitmap font for eufm10 mktexpk: perhaps eufm10 is missing from the map file. ... !pdfTeX error: pdflatex (file eufm10): Fount eufm10 at <line number> not found ==> Fatal error occurred, no output PDF file produced! The manual way to get the euler fonts working is to log in as root and run updmap-sys --enable Map=euler.map
This is biting my users as well now that I've pushed F19. Let me see what I can come up with.
Created attachment 797551 [details] Patch fixing Yeah, the fix is simply to remove the additional five spaces in those two points in the spec.
A big texlive update was just committed and while it touches the very code involved in this problem it preserves the errant spaces. I'm considering just committing the fix myself but this is one of those packages I'm really not sure I should ever touch.
I say go for it. You're just removing five bad spaces from two lines of the spec file...
Looks like Jindrich did commit a fix for this a few hours ago. Thanks!
texlive-2013-1.20131014_r31898.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/texlive-2013-1.20131014_r31898.fc20
texlive-2013-1.20131014_r31898.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/texlive-2013-1.20131014_r31898.fc19
Package texlive-2013-1.20131014_r31898.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing texlive-2013-1.20131014_r31898.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19153/texlive-2013-1.20131014_r31898.fc20 then log in and leave karma (feedback).
texlive-2013-2.20131019_r31948.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/texlive-2013-2.20131019_r31948.fc18
texlive-2013-3.20131021_r31961.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.