# emerge --oneshot =dev-libs/glib-1.2.10-r5 Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/glib-1.2.10-r5 to / >>> md5 src_uri ;-) glib-1.2.10.tar.gz >>> Unpacking source... >>> Unpacking glib-1.2.10.tar.gz to /var/tmp/portage/glib-1.2.10-r5/work * Applying glib-1.2.10-gcc34-fix.patch... [ ok ] >>> Source unpacked. [...] make[2]: Leaving directory `/var/tmp/portage/glib-1.2.10-r5/work/glib-1.2.10/tests' make[1]: Leaving directory `/var/tmp/portage/glib-1.2.10-r5/work/glib-1.2.10' >>> Test phase [not enabled]: dev-libs/glib-1.2.10-r5 touch: cannot touch `.tested': Permission denied !!! ERROR: dev-libs/glib-1.2.10-r5 failed. !!! Function dyn_test, Line 928, Exitcode 1 !!! Failed to 'touch .tested' in /var/tmp/portage/glib-1.2.10-r5 !!! If you need support, post the topmost build error, NOT this status message. emerging with FEATURES="candy userpriv" in make.conf (that is, usersandbox disabled) works as expected. $ emerge info Portage 2.0.51_rc7 (default-x86-1.4, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-20040814 i686) ================================================================= System uname: 2.6.8-20040814 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs candy ccache distlocks sandbox userpriv usersandbox" GENTOO_MIRRORS="ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp.easynet.nl/mirror/gentoo/ http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/ http://gentoo.inode.at/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/local /usr/local/portage/uncleowen" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow X aalib alsa apache2 apm avi bitmap-fonts cdr crypt cups directfb doc dvd dvdr encode esd f77 foomaticdb gd gif gnome gpm gtk gtk2 guile imlib ipv6 java joystick jpeg libg++ libwww mad mikmod mmx mmx2 mpeg ncurses nls nvidia oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell sse sse2 ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xprint xv zlib" Reproducible: Always Steps to Reproduce:
why does it try to touch anything during the testphase while it's disabled. Afaic this is not a gnome problem, give it to portage team or something.
we don't want it! it fails in the non-enabled testing phase... why would the freaking package do anything there. This is not glib.
cd "${BUILDDIR}" touch .tested || die "Failed to 'touch .tested' in ${BUILDDIR}" Portage does this for every phase, regardless of whether there was anything to do. Are you modifying BUILDDIR somehow? Changing permissions? What are the permissions on BUILDDIR when portage dies?
No, I'm not messing with BUILDDIR, it's still /var/tmp/portage/glib-1.2.10-r5 (as can be seen in the error message). Permissions on /var/tmp/portage/glib-1.2.10-r5 are: uo@uo /var/tmp/portage/glib-1.2.10-r5 $ ls -al total 36 drwxr-xr-x 5 portage portage 4096 Oct 11 15:53 . drwxrwxr-x 597 portage portage 20480 Oct 11 15:49 .. -rw-r--r-- 1 portage portage 0 Oct 11 15:53 .compiled -rw-r--r-- 1 root root 0 Oct 10 11:34 .tested -rw-r--r-- 1 portage portage 0 Oct 11 15:49 .unpacked drwxr-xr-x 2 portage portage 4096 Oct 11 15:53 build-info drwxrws--- 2 portage portage 4096 Oct 11 15:53 temp drwx------ 3 portage portage 4096 Oct 11 15:49 work Is it correct, that .testet is owned by root? I'll remove /var/tmp/portage and try again.
That worked :) Seems that was the problem. This is, what I think went wrong: - First, I emerged without userpriv. That created a file .tested owned by root. - Sometime later, I emerged with userpriv. Portage tries to overwrite .tested, but doesn't have enough priviledges. That raises the question: Why isnt .tested removed along with the rest at the begin of the emerge? It should be, shouldn't it?
*** Bug 66231 has been marked as a duplicate of this bug. ***
Appears to have been cause by portage's clean phase not cleaning ".tested". It now does this in 2.0.51.22.
