When I try to emerge xcolor-2.00 it bails with a access violation summary. Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -u xcolor Actual Results: >>> Source unpacked. * Extracting from /var/tmp/portage/xcolor-2.00/work/xcolor/xcolor.ins >>> Test phase [not enabled]: dev-tex/xcolor-2.00 >>> Install xcolor-2.00 into /var/tmp/portage/xcolor-2.00/image/ category dev-tex * Making documentation: ./xcolor1.tex * Making documentation: ./xcolor2.tex * Making documentation: ./xcolor3.tex * Making documentation: ./xcolor.dtx man: prepallstrip: strip: strip --strip-unneeded >>> Completed installing xcolor-2.00 into /var/tmp/portage/xcolor-2.00/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-tex_-_xcolor-2.00-7329.log" mkdir: /usr/share/texmf/fonts/tfm/jknappen mkdir: /usr/share/texmf/fonts/tfm/jknappen/tc --------------------------------------------------------------------------------
Which version of tetex are you using? If you are using tetex-2.0.2-r5, please upgrade to 2.0.2-r6 and try again.
As far as I can see tetex-2.0.2-r6 is not available on stable, or am I wrong? This is what I get: root # emerge -pu tetex These are the packages that I would merge, in order: Calculating dependencies ...done! root # emerge -p tetex These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] app-text/tetex-2.0.2-r5 ------------------------------ So you need to fix the xcolor ebuild?
If you stick to use stable version please remerge tetex-2.0.2-r5. It's the same as -r6 but you need to remerge if you have broken installation at the moment. If you emerged tetex-2.0.2-r5 from 10 Feb to 18 Feb you are likely to have corrupted tetex installation. (i.e. it may or may not xcolor that is broken) Sorry for any inconvenience.
Re-emerging tetex-2.0.2-r5 makes xcolor behave nicely. Works for me...
Thanks for the report. I assume this won't be an issue after marking -r6 stable.
I experienced the same problem with ptex-3.1.4-r2. Re-emerging it also made xcolor behave nicely.
Experienced similar with tetex-3.0-r2 (~x86): --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-tex_-_xcolor-2.00-20311.log" access_wr: /usr/share/texmf/fonts access_wr: /usr/share/texmf/fonts -------------------------------------------------------------------------------- Can be fixed (like other tex sandbox violations) with: VARTEXFONTS="${T}" TEXMFVAR="${T}" USE_TEXMFVAR=1 in /etc/portage/bashrc or in ebuild.
ping
