When I tried to remerge fluxbox with USE="nls", it outputs >>> Completed installing into /var/tmp/portage/fluxbox-0.9.9/image/ * checking 107 files for package collisions existing file /usr/share/fluxbox/nls/en/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/en_US/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/es/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/fr/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/lv/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/POSIX/fluxbox.cat is not owned by this package existing file /usr/share/fluxbox/nls/US_ASCII/fluxbox.cat is not owned by this package * spend 0.181954860687 seconds checking for file collisions * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package x11-wm/fluxbox-0.9.9 NOT merged and fails to merge. /usr/share/fluxbox/nls/{es,fr,lv,en,en_US,POSIX,US_ASCII} are simbolic links to other directories in /usr/share/fluxbox/nls, and the linked directory is owned by x11-wm/fluxbox. Since all of those files shown above are linked to files owned by fluxbox, it is expected to merge even when FEATURES is set to collision-protect.
*** Bug 72813 has been marked as a duplicate of this bug. ***
*** Bug 73421 has been marked as a duplicate of this bug. ***
Please raise the severity of this bug, as it also makes updating gcc-3.4.3 -> gcc-3.4.3-r1 impossible. fn_x@hotmail.com noted in bug #73421 comment 1: gcc 3.4.3 installed in /usr/lib/gcc-lib. gcc 3.4.3-r1 installs in /usr/lib/gcc. /usr/lib/gcc is a symlink to gcc-lib. That's right, see bug #73421 comment 2: [20:27:52 alexander@server:~] $ epm -qf /usr/lib/gcc{,-lib}/i686-pc-linux-gnu/3.4.3/include/emmintrin.h file /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/include/emmintrin.h is not owned by any package gcc-3.4.3 portage complained about /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/include/emmintrin.h
What version of portage?
23:41:36 askwar@alturo:~ $ emerge info Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r3.PHP2.4kb.cleaned.no-preempt.05 i686) ================================================================= System uname: 2.6.9-gentoo-r3.PHP2.4kb.cleaned.no-preempt.05 i686 Intel(R) Celeron(R) CPU 2.00GHz Gentoo Base System version 1.6.6 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 14 2004, 22:41:19)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-fomit-frame-pointer -pipe -O2 -march=pentium4" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo http://194.117.158.29/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="acl apache2 apm arts async avi bzlib crypt cscope cups curl curlwrappers diet djbfft encode exif fam flash foomaticdb ftp fwdzone gd gdbm gif hal hardened iconv imagemagick imap imlib immqt-bc ithreads javascript jpeg libedit libg++ libwww lzo lzw lzw-tiff mad maildir mailwrapper mbox mmap mmx mng mpeg mysql ncurses nls no-old-linux noantlr nobcel nobeanutils nobsh nocommonslogging nocommonsnet nojdepend nojsch nojython nolog4j nooro noregexp norhino noxalan noxerces nptl offensive oggvorbis opengl oss pam parse-clocks pcntl pcre pdflib perl pic pie png posix postgres pwdb python qt quicktime readline recode sasl sdl shared slang sockets spell sse ssl sysvipc tcpd tiff truetype unicode vhosts x86 xfs xml2 xmms xv zlib linguas_de"
In both cases, it looks like the ebuilds created symlinks in the live filesystem from the pkg_postinst phase. Therefore, the ebuilds are to blame. If they are doing this due to some other shortcoming in portage, they that other problem should be fixed. Hacking collision-protect so that it tries to be smart about symlinks will only lead to cases where it isn't smart enough.
*** Bug 92922 has been marked as a duplicate of this bug. ***
