--------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-HTML-Mason-***-*****.log" unlink: /usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Interp.pod unlink: /usr/lib/perl5/site_perl/5.6.1/HTML/Mason/ApacheHandler.pod unlink: /usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pod unlink: /usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Component.pod --------------------------------------------------------------------------------
please post the output of `emerge -V` and `emerge info`
Sorry. Portage 2.0.44 (default-1.0, gcc-2.95.3, glibc-2.2.5-r7) ================================================================= System uname: 2.4.19-gentoo-r9 i686 USE="x86 oss 3dnow apm avi crypt cups encode jpeg libg++ mikmod mmx mpeg ncurses pdflib qtmt quicktime spell truetype xml2 xmms xv alsa arts berkdb bonobo cdr d irectfb esd gdbm gif gnome gnome-libs gpm gtk gtkhtml guile imlib java kde ldap libwww motif mozilla mysql nls oggvorbis opengl pam perl png postgres python qt readline ruby scanner sdl slang ssl svga tcltk tcpd tetex tiff X" ARCH="x86" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"
Matt, adding you to this bug since this was your commit.
Mol, Did you have the older version of Mason installed when you emerged the new one? Or is this a new install of Mason?
This is confirmed - sandbox violation in the final stages of the install.
The problem with previous installations of HTML-Mason already on your system. The new version attempts to delete some outdated pod files, which is a violation of the sandboxing. Looking into work arounds now.
michael, We could put DEPEND="!dev-perl/HTML-Mason" for the short term. It would force the user to unmerge the old instance. Don't know where that is in your scale of bad-hacks though. :) The alternative is to hack up the Makefile and prevent it from trying to rm those old installation files. matt
matt, short term solution works for me. I think long term (this week, just not this afternoon, not for me anyway) would be to hack the Makefile, test, then add an einfo along the lines of "doc1, doc2, doc3, and doc4 were merged into docA" (doc names are in that UPGRADE file somewhere). Can you add the != for now? Mol, it's up to you on whether you can wait a day (I just don't have access to my dev machine right now to make the long term change). unmerging the current HTML-Mason *should* not affect anything you've developed (no liability claims though). Mike
Fixed, in portage. Give it time to hit the mirrors. I'm not proud of the fix - it's a stupid perl trick(tm) but it works fast and efficiently. Please note the einfo at the end of the install regarding legacy pod files. Other than that, let us know if it works for you so this ticket can be closed out.
Is this fixed for you? Just want to be sure before closing this out.
Michael, Sorry for the delay and thanks for a quick fix. The HTML-Mason-1.15-r1 is verified as a nasty and working patch :-)
