Summary: | app-admin/eselect-1.0.11-r1 - The ebuild phase 'unpack' has exited unexpectedly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mark Knecht <markknecht> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jer, pacho, toralf |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 216231 |
Description
Mark Knecht
2008-11-23 21:38:04 UTC
Here we go again. :) This message usually baffles most people so I've updated it to include some more details: * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior * is known to be triggered by things such as failed variable assignments * (bug #190128) or bad substitution errors (bug #200313). Normally, before * exiting, bash should have displayed an error message above. If bash did * not produce an error message above, it's possible that the ebuild has * called `exit` when it should have called `die` instead. This behavior * may also be triggered by a corrupt bash binary or a hardware problem * such as memory or cpu malfunction. If the problem is not reproducible or * it appears to occur randomly, then it is likely to be triggered by a * hardware problem. If you suspect a hardware problem then you should try * some basic hardware diagnostics such as memtest. Please do not report * this as a bug unless it is consistently reproducible and you are sure * that your bash binary and hardware are functioning properly. In essence, you've probably got either a corrupt bash binary or a hardware problem. *** This bug has been marked as a duplicate of bug 205044 *** Bug 205044 was an entirely separate issue. This bug is more similar to bug 244979 and bug 247100. Marking as fixed since the error message is more informative in 2.1.6_rc2, as shown in comment #2. *** Bug 247030 has been marked as a duplicate of this bug. *** |