emerging gimp-2.4.2 from 2.2.17, portage complains that a package file collision occurs. I can't imagine any other packages claiming ownership of /usr/bin/gimp. Reproducible: Always Steps to Reproduce: 1. emerge =gimp-2.2.17 2. emerge =gimp-2.4.2 3. Actual Results: * This package will overwrite one or more files that may belong to other * packages (see list below). Add "collision-protect" to FEATURES in * make.conf if you would like the merge to abort in cases like this. 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/bin/gimp Expected Results: No warnings of file collision. Surely the previous package version owns /usr/bin/gimp. doesn't affect the installation - still works fine.
(In reply to comment #0) > * 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. Please, read the message once again.
(In reply to comment #0) > the previous package version owns > /usr/bin/gimp. equery does not find any package owning /usr/bin/gimp for me but it is a symlink to /usr/bin/gimp-2.2 which belongs to media-gfx/gimp-2.2.17. Possible the collision-protect system must be able to automatically resolve such problems.
Please re-open the bug. The /usr/bin/gimp symlink exists AFTER you uninstall gimp-2.2.17. Since it DOESN'T belong to the gimp package it doesn't get removed.
We won't fix anything here, delete the symlink and move on finally.
*** This bug has been marked as a duplicate of bug 203562 ***
