While updating gnome-base/libbonoboui-2.10.1, I received the following error during the `make check` phase: make check-TESTS make[3]: Entering directory `/var/tmp/portage/libbonoboui-2.10.1/work/libbonoboui-2.10.1/tests' ACCESS DENIED chmod: /root/.gnome2_private Could not set mode 0700 on private per-user gnome configuration directory `/root/.gnome2_private/': Permission denied FAIL: test-ui-auto =================== 1 of 1 tests failed =================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/var/tmp/portage/libbonoboui-2.10.1/work/libbonoboui-2.10.1/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/var/tmp/portage/libbonoboui-2.10.1/work/libbonoboui-2.10.1/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/libbonoboui-2.10.1/work/libbonoboui-2.10.1/tests' make: *** [check-recursive] Error 1 For now, I will work around the bug by merging with FEATURES=-maketest. Hit me up for any additional information which may be useful. The host in question: Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r1, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 AMD Athlon(tm) processor Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -Os -pipe" CHOST="i686-pc-linux-gnu" MAKEOPTS="-j2 -w" The attempted build: [ebuild U ] gnome-base/libbonoboui-2.10.1 [2.10.0] +X -debug +doc -static Running FEATURES='-maketest' emerge --oneshot =gnome-base/libbonoboui-2.10.1 completed without error.
please submit a patch upstream to fix the test. *** This bug has been marked as a duplicate of 69343 ***
Please add RESTRICT=test to ebuild if no other solution seems likely.
If we add that option to packages that don't pass tests then the whole maketest feature is useless. I realise this is a concern to some users, as they don't want to install packages that fail tests or have their installs stopped by the error. The users who are effected should really file upstream bug reports with the package maintainers and inform them that the the package doesn't pass tests or that the tests are out of date. You really shouldn't use maketest globally if you are willing to install packages that fail anyways.
*** Bug 120117 has been marked as a duplicate of this bug. ***
*** Bug 144694 has been marked as a duplicate of this bug. ***
*** Bug 156976 has been marked as a duplicate of this bug. ***
I still disagree with the way this bug was resolved; nevertheless, this one's dead.
