Updating from libX11 1.3.3 to 1.3.4 failed. I suspect the error to be trivial, but I never saw such a thing before, hence the bug, so you can tell me how to deal with it ? Manually delete the file and re-emerge maybe ? Also note that I tried the update to see if my x64-macos was a candidate for the bug 325087, it appears I'm not. Compilation errors: >>> Installing (1 of 1) x11-libs/libX11-1.3.4 * checking 1027 files for package collisions 1000 files checked ... * 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. * * package x11-libs/libX11-1.3.4 NOT merged * * Detected file collision(s): * * /Users/superflo/Gentoo/usr/share/man/man3/XkbGetDetectableAutoRepeat.3.bz2 * /Users/superflo/Gentoo/usr/share/man/man3/XkbSetDetectableAutoRepeat.3.bz2 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'x11-libs/libX11-1.3.4' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. >>> Failed to install x11-libs/libX11-1.3.4, Log file: >>> '/Users/superflo/Gentoo/var/tmp/portage/x11-libs/libX11-1.3.4/temp/build.log'
Actually reading the collision message I pasted, it appears I shouldn't have openned a bug because there is not /two/ files but none, owing the file ? Anyway, this message doesn't tell me how to resolve such problem. "You should simply ignore the collision" : I wish I could, but how ? Removing the file manually ? Doesn't look like ignoring. Help appreciated ;) I'll change the severity to trivial.
To ignore a file collision when no package owns the file, you must use FEATURES="-collision-protect"; to ignore it when another package *does* on the file, you must use FEATURES="-collision-protect -protect-owned"
notabug, user support case was answered in comment #2 :)
