Emerging dev-php/PEAR-DB-1.5.0_rc2 gets sandbox violation on file /usr/share/snmp/mibs/.index (I don't know what this file has to do with php!) Question: Is this similar to bug #28168, that has reappeared with the modifications to the PEAR-DB ebuild? Reproducible: Always Steps to Reproduce: 1. emerge -v PEAR-DB #(using unstable) Actual Results: bash-2.05b# emerge -uDv PEAR-DB Calculating dependencies ...done! >>> emerge (1 of 1) dev-php/PEAR-DB-1.5.0_rc2 to / >>> md5 src_uri ;-) DB-1.5.0RC2.tgz php-pear php-pear >>> Unpacking source... >>> Unpacking DB-1.5.0RC2.tgz to /var/tmp/portage/PEAR-DB-1.5.0_rc2/work >>> Source unpacked. php-pear php-pear >>> Install PEAR-DB-1.5.0_rc2 into /var/tmp/portage/PEAR-DB-1.5.0_rc2/image/ category dev-php ACCESS DENIED open_wr: /usr/share/snmp/mibs/.index no script destination directory man: prepallstrip: strip: >>> Completed installing into /var/tmp/portage/PEAR-DB-1.5.0_rc2/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-PEAR-DB-1.5.0_rc2-12340.log" open_wr: /usr/share/snmp/mibs/.index -------------------------------------------------------------------------------- Expected Results: Should have emerged successfully. Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031212-r0, 2.6.0-gentoo) ================================================================= System uname: 2.6.0-gentoo i686 AMD Athlon(tm) XP 2200+ Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /opt/tomcat/conf /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /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/env.d" CXXFLAGS="-mcpu=athlon-xp -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox usersandbox" GENTOO_MIRRORS="ftp://mirror.iawnet.sandia.gov/pub/gentoo/ http://gentoo.seren.com/gentoo ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d acl acpi acpi4linux alsa amd antlr apache2 apm arts artswrappersuid avi berkdb bonobo cdr crypt cups directfb dnd doc dv dvd dvdr encode esd ethereal evo fbcon fbdev foomaticdb foreign-package foreign-sysvinit freetds gb gd gd-external gdbm gif ginac gnome gnomedb gpm gstreamer gtk gtk2 gtkhtml guile imap imlib innodb ipv6 java jikes jpeg junit kde kerberos ldap libg++ libgda libwww mad maildir mbox mdb mikmod mmx motif mozilla moznoirc moznomail mpeg mysql ncurses nls nptl oci8 odbc ofx oggvorbis opengl oss pam pda pdflib perl pg-hier pic plotutils png postgres ppds python qt quicktime radeon readline ruby ruby18 samba sasl sdk sdl slang slp snmp spell sse ssl svga tcltk tcpd tetex tiff truetype type1 usb wmf wxwindows x86 xml xml2 xmms xv zeo zlib"
Weird, as the new ebuild (=the eclass) doesn't touch P. Might be an issue with usersandbox, or snmp. Can you try building php with USE="-*" and FEATURES="-usersandbox" and then remerging PEAR-DB?
Re: Comment #1: Tal, first I tried: bash-2.05b# USE='-*' FEATURES='-usersandbox' emerge -uDv PEAR-DB This failed with the same message. Then I tried: bash-2.05b# USE='-*' FEATURES='-usersandbox -sandbox' emerge -uDv PEAR-DB This worked successfully. Hope this helps you figure out what's happening.
Ok, try updating php-core (to 4.3.4-r1) and try again.
Re: Comment #3: Tal, after updating php-core, I re-emerged PEAR-DB without any problem. So whatever this did seems to fix my problem. Thanks. Happy Holidays!
