Bug 223685 – After long emerge sys-apps/portage-2.1.5.2 does not show build errors at the bottom

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Rada 2008-05-26 13:44:42 UTC]

After doing an emerge -uD world or something, if a package fails, it is only obvious if I scroll up above all the ebuild messages to the error. The error *or at least recognition that x package failed) should be shown below the ebuild messages.

Reproducible: Always

Steps to Reproduce:
1. emerge -e world
2. have a package fail
3. you wont know until you scroll up, that's if you do.

Actual Results:  
error way at the top

Expected Results:  
error at the bottom

[Comment 1 Zac Medico 2008-05-27 00:29:41 UTC]

This should mostly be solved by the fix for bug #197905.

However, if the merge is killed by a sandbox violation then there is no die message logged via eerror. In this case, an "ACCESS VIOLATION SUMMARY" is displayed bug not logged, and it can be obscured by elog messages that are displayed after it. Perhaps this is the case you are referring to?

[Comment 2 Zac Medico 2008-05-27 00:36:31 UTC]

I've just noticed that the logging behavior varies depending on whether or not the --buildpkg option is enabled, so that could be be something you noticed (more specific example would help).

[Comment 3 Zac Medico 2008-05-27 00:53:37 UTC]

Created attachment 154403 [details, diff]
make sure elog messages always get collected

If this patch is saved as /tmp/elog.patch, then it can be applied as follows:

patch /usr/lib/portage/bin/emerge /tmp/elog.patch

[Comment 4 Zac Medico 2008-06-01 10:44:02 UTC]

This is fixed in 2.1.5.3.