It is easier to show you: * The following 7 packages have failed to build or install: <snip> * ('ebuild', '/', 'media-libs/x264-0.0.20090629', 'merge'), Log file: * '/public/tmp/linux-64/portage/media-libs/x264-0.0.20090629/temp/build.log' * ('ebuild', '/', 'x11-libs/libX11-1.2.2', 'merge'), Log file: * '/public/tmp/linux-64/portage/x11-libs/libX11-1.2.2/temp/build.log' * ('ebuild', '/', 'x11-libs/libXext-1.0.5', 'merge') * ('ebuild', '/', 'x11-misc/xscreensaver-5.10', 'merge'), Log file: * '/public/tmp/linux-64/portage/x11-misc/xscreensaver-5.10/temp/build.log' In this case, behind libXext it would be nice to say "Missing dependencies due to failure" or similar. Can this be done?
%% emerge --version Portage 2.2.00.14200-prefix (prefix/linux/amd64, gcc-4.4.1, unavailable, 2.6.9-55.ELsmp x86_64)
There is output before that last block you quoted, where portage says: * emerge --keep-going: cat/pkg-ver dropped due to unsatisfied * dependency. If that is not sufficient (I am not sure whether the output is repeated after a long emerge with lots of other output), maybe the list of "packages [that] have failed to build or install" could be divided into groups with more detailed headings? Like: * The following X packages have failed to build or install: * ... could not be merged into the system: * ... were dropped due to unsatisfied dependencies:
(In reply to comment #2) > There is output before that last block you quoted, where portage says: > * emerge --keep-going: cat/pkg-ver dropped due to unsatisfied > * dependency. > > If that is not sufficient (I am not sure whether the output is repeated > after a long emerge with lots of other output), It's logged via eerror, so it will be echoed by the mod_echo elog module before emerge exits, and you can also find the messages in /var/log/portage/elog/summary.log. > maybe the list of "packages > [that] have failed to build or install" could be divided into groups with > more detailed headings? Like: > > * The following X packages have failed to build or install: > * ... could not be merged into the system: > * ... were dropped due to unsatisfied dependencies: Yeah, we could do that. The eerror messages are currently generated inside _calc_resume_list in pym/_emerge/Scheduler.py.
