Updateing fpc to version 2.0.4 fails due to not being able to write into /var/cache/fonts -- access denied. Over the last week I have manually created some of the directories required and changed permissions so anybody or any user can update. However, the ebuild always fails. Perhaps I am doing something wrong. I am using: Portage 2.1.1_rc1-r5 (default-linux/x86/2006.0, gcc-4.1.1/vanilla, glibc-2.4-r3, 2.6.17-gentoo-r7 i686) System uname: 2.6.17-gentoo-r7 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.12.4 Last Sync: Wed, 06 Sep 2006 20:00:01 +0000 ccache version 2.4 [enabled] app-admin/eselect-compiler: 2.0.0_rc2-r1 dev-lang/python: 2.4.3-r3 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r2 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17 ACCEPT_KEYWORDS="x86 ~x86" The error is:- This is METAFONT, Version 2.71828 (Web2C 7.5.5) kpathsea: Running mktexmf ecrm1000 ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf9571.tmp /usr/bin/mktexmf: line 92: mf9571.tmp: Permission denied chmod: cannot access `mf9571.tmp': No such file or directory mv: cannot stat `mf9571.tmp': No such file or directory mktexmf: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf: successfully generated. /var/lib/texmf/web2c/mktexupd: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf not a file. warning: kpathsea: mktexmf output `/var/cache/fonts/source/jknappen/ec/ecrm1000.mf' instead of a filename. ! I can't find file `ecrm1000'. <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000 Please type another input file name ! Emergency stop. <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000 Transcript written on mfput.log. grep: ecrm1000.log: No such file or directory mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000' failed to make ecrm1000.tfm. kpathsea: Appending font creation commands to missfont.log. ! Font T1/cmr/m/n/10=ecrm1000 at 10.0pt not loadable: Metric (TFM) file not fou nd. <to be read again> relax l.100 \fontencoding\encodingdefault\selectfont ? Thanks Paul
Which version of tex do you have installed?
I have Tex 3.141592 (web2C 7.5.5) Hope this helps Paul
Sorry for not being clear, I was hoping for the version of the Gentoo package. What does `emerge --pretend --verbose virtual/tetex` show?
Sorry I should have provided that info as well. [ebuild R ] app-text/tetex-3.0_p1-r3 USE="X doc motif -Xaw3d -lesstif -neXt -tk" 0 kB regards Paul
Same error here: ... This is METAFONT, Version 2.7182 (Web2C 7.4.5) kpathsea: Running mktexmf ecrm1000 ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf19629.tmp /usr/bin/mktexmf: line 92: mf19629.tmp: Permission denied chmod: cannot access `mf19629.tmp': No such file or directory ACCESS DENIED unlink: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf rm: cannot remove `ecrm1000.mf': Permission denied mv: cannot stat `mf19629.tmp': No such file or directory mktexmf: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf: successfully generated. /usr/share/texmf/web2c/mktexupd: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf not a file. warning: kpathsea: mktexpk output `/var/cache/fonts/source/jknappen/ec/ecrm1000.mf' instead of a filename. ! I can't find file `ecrm1000'. <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000 Please type another input file name ! Emergency stop. <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000 Transcript written on mfput.log. mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000' failed. kpathsea: Appending font creation commands to missfont.log. ! Font T1/cmr/m/n/10=ecrm1000 at 10.0pt not loadable: Metric (TFM) file not fou nd. <to be read again> relax l.95 \fontencoding\encodingdefault\selectfont ? Then after quiting tex: ... ? quit OK, entering batchmodemake: *** [user.pdf] Error 1 !!! ERROR: dev-lang/fpc-2.0.4 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile fpc-2.0.4.ebuild, line 89: Called die !!! make pdf failed! !!! If you need support, post the topmost build error, and the call stack if relevant. --------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/var/log/sandbox/sandbox-dev-lang_-_fpc-2.0.4-15991.log" open_wr: /var/cache/fonts/source/jknappen/ec/mf19629.tmp unlink: /var/cache/fonts/source/jknappen/ec/ecrm1000.mf -------------------------------------------------------------------------------- There seems to be some problem with the sandbox, so I tried: FEATURES="-sandbox" emerge fpc This works here on the AMD64, fpc is now emerged. I am on an AMD64 with GCC 4.1.1 and GLIBC 2.4, at the moment. I got the same error on my PPC. I don't think this is platform-dependent, this seems to be a tetex-problem. But on my PPC, it doesn't help to deactivate sandbox, this doesn't work. I will post this error later (it was different, but my mind says it was also tetex-related). This is my tetex-version (on the AMD64): [ebuild R ] app-text/tetex-2.0.2-r9 USE="X -doc -tk%" 0 kB -- Albert
Oddly, I started getting these sandbox errors now without even changing my Tex installation at all. Fixed by using pregenerated docs, and that should also fix whatever the other problem from comment #5 is.
Forgot to close this :)
*** Bug 146991 has been marked as a duplicate of this bug. ***
I have now installed fpc on my machine using :- FEATURES="-sandbox" emerge fpc This seems to be a workaround on c86 and ~x86 based machines. Paul
> I have now installed fpc on my machine using :- FEATURES="-sandbox" emerge fpc > This seems to be a workaround on c86 and ~x86 based machines. This bug is already fixed, if you're still having problems with fpc and sandbox, please run `emerge --sync` and retry.
Thanks for the reply, I have just sync'd and it wants to "UD" from my now installed 2.0.4 to 2.0.2 Has the wrong version been updated? regards Paul
> Thanks for the reply, > I have just sync'd and it wants to "UD" from my now installed 2.0.4 to 2.0.2 > Has the wrong version been updated? 2.0.4 has the same keywords as 2.0.2, so if you can emerge 2.0.2, you can emerge 2.0.4 unless you locally mask it. You may have something (lazarus?) installed that depends on fpc-2.0.2 specifically. But this has nothing to do with this bug anymore. :)
