Summary: | eclass-debug.log should not be created in / | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Bruce A. Locke (RETIRED) <blocke> |
Component: | Unclassified | Assignee: | Dan Armak (RETIRED) <danarmak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | danielsabo, drobbins |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bruce A. Locke (RETIRED)
2002-07-12 22:03:16 UTC
I see it... Please look at debug-print() in ebuild.sh. I don't see how or why the log file ends up in /, it should go in $T and it does go there but a copy is in /! Wierdest thing is, it isn't caught by the sandbox. I'm really puzzled by this... any idea? I can't reproduce it at will either, but once in a while /eclass-debug/log appears again. I'll try to catch it the next time. Just confirming that this bug still exists, and is still annoying ;). $emerge --version Portage 2.0.22 drobbins told me why this happens: it turns out $T (=$WORKDIR/temp) isn't defined when emerge sources an ebuild oly for dep calculation. So piping > $T/eclass-debug.log put the file in /. I've fixed this in ebuild.sh in gentoo-src and it should be included in the next portage (2.0.27). This is fixed in the latest portage versions. |