1 |
Author: zmedico |
2 |
Date: 2008-11-26 18:29:20 +0000 (Wed, 26 Nov 2008) |
3 |
New Revision: 12101 |
4 |
|
5 |
Modified: |
6 |
main/trunk/pym/portage/__init__.py |
7 |
Log: |
8 |
Add some more clarification to the 'ebuild phase exited unexpectedly' message. |
9 |
|
10 |
|
11 |
Modified: main/trunk/pym/portage/__init__.py |
12 |
=================================================================== |
13 |
--- main/trunk/pym/portage/__init__.py 2008-11-26 07:02:16 UTC (rev 12100) |
14 |
+++ main/trunk/pym/portage/__init__.py 2008-11-26 18:29:20 UTC (rev 12101) |
15 |
@@ -5142,9 +5142,20 @@ |
16 |
"is known to be triggered " + \ |
17 |
"by things such as failed variable " + \ |
18 |
"assignments (bug #190128) or bad substitution " + \ |
19 |
- "errors (bug #200313). This behavior may also be " + \ |
20 |
- "triggered by a corrupt bash binary or a hardware " + \ |
21 |
- "problem such as memory or cpu malfunction." |
22 |
+ "errors (bug #200313). Normally, before exiting, bash should " + \ |
23 |
+ "have displayed an error message above. If bash did not " + \ |
24 |
+ "produce an error message above, it's possible " + \ |
25 |
+ "that the ebuild has called `exit` when it " + \ |
26 |
+ "should have called `die` instead. This behavior may also " + \ |
27 |
+ "be triggered by a corrupt bash binary or a hardware " + \ |
28 |
+ "problem such as memory or cpu malfunction. If the problem is not " + \ |
29 |
+ "reproducible or it appears to occur randomly, then it is likely " + \ |
30 |
+ "to be triggered by a hardware problem. " + \ |
31 |
+ "If you suspect a hardware problem then you should " + \ |
32 |
+ "try some basic hardware diagnostics such as memtest. " + \ |
33 |
+ "Please do not report this as a bug unless it is consistently " + \ |
34 |
+ "reproducible and you are sure that your bash binary and hardware " + \ |
35 |
+ "are functioning properly." |
36 |
return msg |
37 |
|
38 |
def _doebuild_exit_status_check_and_log(settings, mydo, retval): |