preparealldocs script was converted to an eclass function, however improper Reproducible: Always Steps to Reproduce: emerging a concerned package i.e. x11-proto/dri2proto just leaves you alone with... Actual Results: >>> Install dri2proto-1.99.3 into /var/tmp/portage/x11-proto/dri2proto-1.99.3/image/ category x11-proto make[1]: Entering directory `/var/tmp/portage/x11-proto/dri2proto-1.99.3/work/dri2proto-1.99.3' make[1]: Nothing to be done for `install-exec-am'. test -z "/usr/include/X11/extensions" || /bin/mkdir -p "/var/tmp/portage/x11-proto/dri2proto-1.99.3/image//usr/include/X11/extensions" /usr/bin/install -c -m 644 'dri2proto.h' '/var/tmp/portage/x11-proto/dri2proto-1.99.3/image//usr/include/X11/extensions/dri2proto.h' /usr/bin/install -c -m 644 'dri2tokens.h' '/var/tmp/portage/x11-proto/dri2proto-1.99.3/image//usr/include/X11/extensions/dri2tokens.h' test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/var/tmp/portage/x11-proto/dri2proto-1.99.3/image//usr/lib/pkgconfig" /usr/bin/install -c -m 644 'dri2proto.pc' '/var/tmp/portage/x11-proto/dri2proto-1.99.3/image//usr/lib/pkgconfig/dri2proto.pc' make[1]: Leaving directory `/var/tmp/portage/x11-proto/dri2proto-1.99.3/work/dri2proto-1.99.3' * The ebuild phase 'install' 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. Expected Results: at least a clear die message the 'exit' statements should be replaced by 'return' since it isn't a script any longer but an eclass function now.
ping.
ok. I was too late.
