| Summary: | tetex-3.0_p1-r2 sandbox violation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | renean |
| Component: | New packages | Assignee: | Text-Markup Team (OBSOLETE) <text-markup+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
renean
2006-03-07 01:42:06 UTC
I can't seem to reproduce this. I'm pretty sure it is not the ebuild that causes the sandbox violation. So it must be somewhere in tetex. Could you try to locate excatly where the problems is, by going to /var/tmp/portage/tetex-3.0_p1-r2/work/tetex-src-3.0, grep around and see if you can figure out what tries to create /web2c and why. I looked in the configs and grepped around, but that brought a lot of lines containing web2c, some in union with shell/makevariables, but I could not determine where they are set first in the process. I came to the conclusion, that somehow the configure of tetex must look in the system an find some illegal configs from former installations. So I unmerged the installed tetex and cleaned my drive from all files and directories containing either tetex, texmf or latex and emerged tetex again. That solved the problem. |