Just tried to install mozilla-firefox-1.0.7-r4 on an amd64 system. It compiles fine and gets installed into the root directory, but the post-build cleaning step fails with the following output: >>> /usr/share/doc/mozilla-firefox-1.0.7-r4/ >>> /usr/share/doc/mozilla-firefox-1.0.7-r4/LEGAL.gz >>> /usr/share/doc/mozilla-firefox-1.0.7-r4/LICENSE.gz --- /usr/include/ --- /etc/ --- /etc/env.d/ >>> /etc/env.d/10MozillaFirefox Updating firefox chrome registry... >>> Regenerating /etc/ld.so.cache... >>> www-client/mozilla-firefox-1.0.7-r4 merged. >>> Recording www-client/mozilla-firefox in "world" favorites file... Traceback (most recent call last): File "/usr/bin/emerge", line 3228, in ? mydepgraph.merge(pkglist) File "/usr/bin/emerge", line 1954, in merge retval=portage.doebuild(y,"clean",myroot,self.pkgsettings,edebug,cleanup=1,tree="porttree") File "/usr/lib/portage/pym/portage.py", line 2505, in doebuild shutil.rmtree(mysettings["T"]) File "/usr/lib/python2.4/shutil.py", line 163, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.4/shutil.py", line 172, in rmtree onerror(os.rmdir, path, sys.exc_info()) File "/usr/lib/python2.4/shutil.py", line 170, in rmtree os.rmdir(path) OSError: [Errno 39] Directory not empty: '/var/tmp/portage/mozilla-firefox-1.0.7-r4/temp/orbit-root' emerge info: Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r5 x86_64) ================================================================= System uname: 2.6.14-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 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.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /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/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ ftp://212.219.56.152/sites/www.ibiblio.org/gentoo/ http://212.219.56.162/sites/www.ibiblio.org/gentoo/" LANG="de_DE@euro" LC_ALL="de_DE@euro" LINGUAS="de" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X Xaw3d aac aalib alsa audiofile avi berkdb bitmap-fonts bzip2 cairo cdr crypt cups curl dts dvd dvdr dvdread eds emboss encode exif expat fam ffmpeg flac foomaticdb fortran gd gdbm gif glut gpm gstreamer gtk gtk2 gtkhtml hal idn imagemagick imlib ipv6 jack jpeg jpeg2k kde lcms libwww lzw lzw-tiff mad mhash mng mp3 mpeg mysql ncurses nls nptl ogg openal opengl pam pcre pdflib perl png python qt quicktime readline sdl spell ssl svg tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev usb userlocales v4l vcd vorbis wmf xine xinerama xml xml2 xpm xv xvid zlib linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, MAKEOPTS emerge -pv mozilla-firefox: [ebuild R ] www-client/mozilla-firefox-1.0.7-r4 -debug -gnome +ipv6 -java -mozcalendar +mozdevelop -moznoxft +mozsvg +truetype +xinerama -xprint
Appears to be an issue in portage nothing mozilla related. zmedico please advise.
It seems that a child process of one of the ebuild phases (perhaps postinst or prerm) continued to run in the background. Well behaved ebuild phases should not leave child processes running in the background like that. Portage should handle it better, but still, ebuild phases should behave better.
Please upgrade to the latest stable version (via anarchy)
