Summary: | portgage fails to emerge ANY ebuild [patch] | ||
---|---|---|---|
Product: | Portage Development | Reporter: | David Douard <douard> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Douard
2007-03-10 10:38:14 UTC
That makes no sense. That change shouldn't have any effect on anything. Both ways are proper syntax. (In reply to comment #1) > That makes no sense. That change shouldn't have any effect on anything. Both > ways are proper syntax. > I'm sorry about this response... It may make no sense, however, my system used to be useless before I did this simple correction, and now it works fine. Take it the way you want, that's a fact on my system (amd64 BTW). I don't know if this actually comes from a bug from bash, or another strange side effect caveat, but things happened the way I told (in a very poor english with many typos and missing words, I must admit. Sorry about that). This kind of reaction does not encourage me to try to help... Yours, Davis And if you revert that change it breaks again? It's just *very* hard to believe that this change has any effect. Something wrong with bash? |