When trying to emerge app-text/linuxdoc-tools, emerge dies after building and installing into the image directory: [...] kpathsea: Running mktexmf ecbx1200 ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf21122.tmp /usr/bin/mktexmf: line 92: mf21122.tmp: Permission denied chmod: cannot access `mf21122.tmp': No such file or directory ACCESS DENIED unlink: /var/cache/fonts/source/jknappen/ec/ecbx1200.mf rm: cannot remove `ecbx1200.mf': Permission denied mv: cannot stat `mf21122.tmp': No such file or directory mktexmf: /var/cache/fonts/source/jknappen/ec/ecbx1200.mf: successfully generated. /usr/share/texmf/web2c/mktexupd: /var/cache/fonts/source/jknappen/ec/ecbx1200.mf not a file. warning: kpathsea: mktexpk output `/var/cache/fonts/source/jknappen/ec/ecbx1200.mf' instead of a filename. ! I can't find file `ecbx1200'. [...] kpathsea: Running mktexmf ecti1000 ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf21296.tmp /usr/bin/mktexmf: line 92: mf21296.tmp: Permission denied chmod: cannot access `mf21296.tmp': No such file or directory ACCESS DENIED unlink: /var/cache/fonts/source/jknappen/ec/ecti1000.mf rm: cannot remove `ecti1000.mf': Permission denied mv: cannot stat `mf21296.tmp': No such file or directory mktexmf: /var/cache/fonts/source/jknappen/ec/ecti1000.mf: successfully generated. /usr/share/texmf/web2c/mktexupd: /var/cache/fonts/source/jknappen/ec/ecti1000.mf not a file. warning: kpathsea: mktexpk output `/var/cache/fonts/source/jknappen/ec/ecti1000.mf' instead of a filename. ! I can't find file `ecti1000'. [...] prepallstrip: strip: i686-pc-linux-gnu-strip --strip-unneeded strip: i686-pc-linux-gnu-strip --strip-unneeded usr/bin/sgmlpre usr/bin/rtf2rtf usr/bin/sgmlsasp >>> Completed installing linuxdoc-tools-0.9.21 into /var/tmp/portage/linuxdoc-tools-0.9.21/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-app-text_-_linuxdoc-tools-0.9.21-16064.log" open_wr: /var/cache/fonts/source/jknappen/ec/mf16421.tmp unlink: /var/cache/fonts/source/jknappen/ec/ectt1000.mf open_wr: /var/cache/fonts/source/jknappen/ec/mf16595.tmp unlink: /var/cache/fonts/source/jknappen/ec/ecrm2074.mf [...] I will attach the complete sandbox-app-text_-_linuxdoc-tools-0.9.21-16064.log. The 'tetex' USE flag is set, though access violations also occur with '-tetex'.
Created attachment 68411 [details] sandbox-app-text_-_linuxdoc-tools-0.9.21-16064.log
I confirm the same incorrect behaviour. The problem with emerging the package stops me from generating PDF documents for pam-0.78-r2. This has one more side effect: even though I have +doc in USE flags, no developer's or module writer's documentation is generated. Most probably because the linuxdoc-tools are not available (yet). Please, fix the linuxdoc-tools-0.9.21.ebuild and upgrade it to -r1 version. Maybe one of the solutions (or patches) mentioned in bug #88232 would help?
Created attachment 70987 [details, diff] files/linuxdoc-tools-0.9.21-nodoc.patch Thanks for pointing out this older bug; Josh Nichols already addressed the problem in bug 88232, comment #7. I slightly modified his patch (because it depends on an earlier patch by him) which simply disables documentation generation. I don't know a better solution at the moment; the problem is: make install runs the installed linuxdoc-tool sgml2latex itself to generate documentation for linuxdoc-tools... This in turn runs tetex's mktexmf, which is responsible for the observed sandbox violations by writing into some font cache directory (/var/cache/fonts/source/...). Maybe this can be prevented in some way?
Created attachment 70988 [details] linuxdoc-tools-0.9.21.ebuild Modified ebuild that applies the -nodoc patch.
Another remark: The Fedora Core patches look quite useful to me (http://cvs.fedora.redhat.com/viewcvs/devel/linuxdoc-tools/). Most of them address upstream bugs referred to via the FC CVS log entries and the FC bug tracking system (https://bugzilla.redhat.com/bugzilla/). Marking the bug as "major" as the current ebuild doesn't even emerge, ie. a complete show-stopper.
I can't reproduce this on a couple of systems. Please attach the complete output from 'emerge linuxdoc-tools', and paste the output from 'emerge --info' in your system. Thanks.
Created attachment 72200 [details] emerge_linuxdoc-tools.log emerge --nocolor linuxdoc-tools 2>&1 | tee emerge_linuxdoc-tools.log
Created attachment 72202 [details] emerge_info Output of emerge info.
I see the problem now, it seems like you have tetex-2 in your system, which is producing those access violations. Could you please upgrade to tetex-3 and see if the problem persists? Thanks.
Upgrading to (~x86) tetex-3.0-r3 solved the problem, linuxdoc-tools-0.9.21 emerges without any problems now. Though I wonder why the access violations also showed up with "-tetex" in the USE flags; IF tetex is installed, it obviously must be a >=3.0 version, and as Portage doesn't allow that kind of dependency, - a dependency on >=app-text/tetex-3.0 should be enforced (ignoring a 'tetex' USE flag), or - the Makefile.in should be patched with my patch (attachment 70987 [details, diff]) in case "-tetex" is set.
The dependency has been fixed in CVS, thanks for the info. Regarding the proposed patch, it is not a proper fix, and not installing any documentation doesn't seem reasonable, with or without tetex. Please let us know if you have a patch that fixes the actual sandbox violation problems, though.
Ah, nice. I didn't think of a !< dependency, good solution.
