Mozilla crashed. You suck! Also, trying to emerge X, portage was emerging xdpyinfo (and I assume it had already emerged xdriinfo or I had it previous to X) and portage decided that the 2 packages owned the same files (/usr/share/man.ecompress.dir, /usr/share/doc.ecompress.dir) which made it throw an error and made me hate wheaties. Reproducible: Always Steps to Reproduce: 1. emerge =x11-apps/xdriinfo-1.0.2 2. emerge =x11-apps/xdpyinfo-1.0.3 3. Actual Results: portage throws error (imagine lots of red): * Messages for package x11-apps/xdpyinfo-1.0.3: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/man.ecompress.dir * /usr/share/doc.ecompress.dir * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-apps/xdriinfo-1.0.2 * /usr/share/doc.ecompress.dir * /usr/share/man.ecompress.dir * * Package 'x11-apps/xdpyinfo-1.0.3' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. * GNU info directory index is up-to-date. Expected Results: xdpyinfo should have compiled I think I might have at one point emerged X, but I don't remember...
Created attachment 168682 [details] emerge --info
I'm not yet sure why those files exist, but they don't belong there. As a workaround, you can manually remove those files.
Could you attach a build log from either one of those packages? It might contain some sort of clue about why those files got installed.
Please reopen if you can reproduce and provide some for info.
In bug #255775 we've found that this is triggered by xargs breakage.
*** This bug has been marked as a duplicate of bug 255775 ***