While doing an "emerge --deep -u world", the first package I need to upgrade is x11-base/xfree-4.2.1-r2 During the compile I get errors semi-frequently like the four below. Always these four in this block, possibly once per new directory being compiled in the build. ACCESS DENIED: chown /var/cache/edb ACCESS DENIED: chown /var/cache/edb/dep ACCESS DENIED: open_wr /var/cache/edb/mtimes ACCESS DENIED: chown /var/cache/edb/mtimes At the end on the build it prints these errors for many pages (more then my scroll buffer), possibly as an error report and then just returns to the command prompt, with no further comment. Reproducible: Always Steps to Reproduce: 1. emerge --deep -u world (emerges x11-base/xfree-4.2.1-r2) Actual Results: Recieve the following erro many times during the build: ACCESS DENIED: chown /var/cache/edb ACCESS DENIED: chown /var/cache/edb/dep ACCESS DENIED: open_wr /var/cache/edb/mtimes ACCESS DENIED: chown /var/cache/edb/mtimes Expected Results: Sucsessfully built the program and installed it. I am guessing that this is a sandbox issue, but am not sure. Here is the output from "emerge info": Portage 2.0.43 (default-x86-1.4, gcc-3.2.1, glibc-2.2.5-r7) ================================================================= System uname: 2.4.19-gentoo-r9 i686 Pentium III (Coppermine) USE="sse mmx apm pcmcia pnp pda gphoto2 cdr scanner cups slp X opengl xv dga fbcon directfb qt qtmt gnome gtk bonobo evo gtkhtml motif tcltk aalib imlib ncurses readline sdl svga lcms gif jpeg png tiff gd avi mpeg quicktime alsa oss ggi dvd xmms oggvorbis flash encode snmp ggz pam ssl crypt imap ldap mbox tcpd mozilla mozctl mozirc mozxmlterm spell truetype xml xml2 pdflib tetex java perl python libwww libg++ berkdb mysql oci8 odbc innodb gdbm samba doc gpm zlib" ARCH="x86" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CXXFLAGS="-march=pentium3 -O3 -pipe" ACCEPT_KEYWORDS="x86" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi g /usr/kde/3/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" MAKEOPTS="-j2" JDK_HOME="" JAVA_HOME="/opt/blackdown-jre-1.3.1" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"
update your portage *** This bug has been marked as a duplicate of 13013 ***
After submitting this, I updated portage and re-did the emerge and it does seem to be running properly. Is there a good reason not to have an emerge always update portage to the most recent stable release before emergeing other things (at least with a flag --upportage)?
nick: read comment #2 ... i would see it as being a good thing the majority of the time but the only reason i havent suggested it is because i know some people may not like having a package being forced on them ...
actually comment #2 is now Bug 15278
