app-emacs/planner-3.41-r2 will not build. Reproducible: Always Steps to Reproduce: 1. Atempt to emerge app-emacs/planner Actual Results: In toplevel form: planner-timeclock-summary.el:75:1:Error: Cannot open load file: schedule Finished loading /usr/share/emacs/site-lisp/egg/leim-list.el and load others... Loading /usr/share/emacs/22.3/leim/leim-list.el (source)... In toplevel form: planner-timeclock.el:47:1:Error: Cannot open load file: schedule Finished loading /usr/share/emacs/site-lisp/egg/leim-list.el and load others... Loading /usr/share/emacs/22.3/leim/leim-list.el (source)... In toplevel form: planner-xtla.el:42:1:Error: Cannot open load file: xtla emacs -q --no-site-file -batch -l ./scripts/planner-build.el \ -f planner-elint-files planner-*.el Finished loading /usr/share/emacs/site-lisp/egg/leim-list.el and load others... Loading /usr/share/emacs/22.3/leim/leim-list.el (source)... Cannot open load file: gnats make: *** [test] Error 255 * * ERROR: app-emacs/planner-3.41-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_test * environment, line 819: Called _eapi0_src_test * ebuild.sh, line 622: Called die * The specific snippet of code: * hasq test $FEATURES && die "Make test failed. See above for details." * The die message: * Make test failed. See above for details. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-emacs/planner-3.41-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emacs/planner-3.41-r2/temp/environment'. Expected Results: successful merge
Created attachment 181934 [details] build.log
Created attachment 181935 [details] ebuild environment
Created attachment 181937 [details] emerge --info
This is not easily fixable in a proper way, since running the tests will require packages as dependencies that are not in Portage (like gnats) or that we have removed earlier (like app-emacs/xtla). Added RESTRICT="test" for now, and version bumped to 3.42. Thank you for reporting the issue.
