I tried the update but got sandbox failures, so I figured you guys could get that working. ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf10184.tmp /usr/bin/mktexmf: line 92: mf10184.tmp: Permission denied chmod: cannot access `mf10184.tmp': No such file or directory ACCESS DENIED unlink: /var/cache/fonts/source/jknappen/ec/ecbx1000.mf rm: cannot remove `ecbx1000.mf': Permission denied mv: cannot stat `mf10184.tmp': No such file or directory etc..
From the description you provide, I think the opposite is actually happening; linuxdoc-tools causes sandbox violations with tetex-2, but not with tetex-3. This should work correctly due to the new restrictions in the dependencies brought by bug #105905. Could you verify if this is still failing (and that you have tetex-3 installed)? Thanks.
Created attachment 77013 [details] linuxdoc-tools-0.9.21.0.1.ebuild I've attached the ebuild I'm using. donnie@supernova coot-0.0.33 $ equery list tetex [ Searching for package 'tetex' in all categories among: ] * installed packages [I--] [ ] app-text/tetex-3.0-r4 (0) donnie@supernova coot-0.0.33 $ emva linuxdoc-tools These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] app-text/linuxdoc-tools-0.9.21.0.1 USE="tetex" 0 kB [3] ... This is METAFONT, Version 2.71828 (Web2C 7.5.4) kpathsea: Running mktexmf ecbx1000 ACCESS DENIED open_wr: /var/cache/fonts/source/jknappen/ec/mf860.tmp /usr/bin/mktexmf: line 92: mf860.tmp: Permission denied chmod: cannot access `mf860.tmp': No such file or directory ACCESS DENIED unlink: /var/cache/fonts/source/jknappen/ec/ecbx1000.mf rm: cannot remove `ecbx1000.mf': Permission denied mv: cannot stat `mf860.tmp': No such file or directory mktexmf: /var/cache/fonts/source/jknappen/ec/ecbx1000.mf: successfully generated.
I have just tried it, after renaming the ebuild to linuxdoc-tools-0.9.21.0.2.ebuild since version -0.1 seems to have disappeared from the debian servers, and I still can't reproduce the problem. Could you try also with -0.2 and attach the full output from emerge?
Created attachment 77037 [details] 8480-linuxdoc-tools-0.9.21.0.2.log (In reply to comment #3) > I have just tried it, after renaming the ebuild to > linuxdoc-tools-0.9.21.0.2.ebuild since version -0.1 seems to have disappeared > from the debian servers, and I still can't reproduce the problem. Could you try > also with -0.2 and attach the full output from emerge? With 0.2 I couldn't get far enough to hit the sandbox problem. I ran into a memory leak during the build, which used up my whole gig of memory and then oom killer came in. Here's the log from that.
Created attachment 81403 [details, diff] move to linuxdoc-tools-0.9.21-r1 to include debian patches. May be it's worth to try to include some patches comming from debian bugzilla. In the current state linux-tools does not allow to build iproute2 documentation. So this attachment adds patch for ebuild to include patching of sources.
Created attachment 81404 [details] And this is tarball with some debian fixes.
Donnie. Can you try that patches? You need to copy tarball with fixes into $DISTDIR and create new ebuild (linuxdoc-tools-0.9.21-r1). That should fix tetex3 problems. BTW. I cann't reproduce your bug.
Created attachment 81994 [details] 7926-linuxdoc-tools-0.9.21.log With the patches it appears to get a bit farther (or rather, it shows more error messages before getting caught in an infinite loop).
Sorry for the lack of support here. What's the status of this problem with the versions of linuxdoc-tools/tetex currently in the tree?
Personally I don't care anymore because Xorg docs no longer use linuxdoc, they switched to docbook.
Great, closing as WFM then.
