Summary: | Cannot unmerge | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kim Pedersen <k.epost> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kim Pedersen
2007-03-09 12:25:28 UTC
Funny thing: I can use "tee" as in e.g.: echo "kim" | tee test.test but which tee returns which: no tee in ((null)) I'd say it's pretty obvious *why* you get the traceback: portage_exception.CommandNotFound: tee Did you mess with PATH? Do you have /usr/bin/tee? You should, since it's part of coreutils. If you don't, you've probably done something bad to your system. If for some reason you don't have tee, you can use the busybox tee to "fix" coreutils: ln -s /bin/busybox /usr/bin/tee > returns
> which: no tee in ((null))
That tells me that your PATH is screwed up, but even with an empty path, I don't get that output.
agaffney@kagome ~ $ PATH= /usr/bin/which tee
/usr/bin/which: no tee in ()
I can get it if I set PATH="(null)", however.
Thanks #2 your trick worked. I *might* have messed up my system. But I can't think of anything that I have done wrong as I run a stable system and always follow emerge log advises. But you probably know better, and your trick fixed my problem so FIXED or me. Anyway, not a portage bug... |