* Messages for package kde-base/knetworkconf-4.1.2: * 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/lib/pkgconfig/system-tools-backends.pc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-admin/system-tools-backends-1.4.2-r1 * /usr/lib/pkgconfig/system-tools-backends.pc * * Package 'kde-base/knetworkconf-4.1.2' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. Reproducible: Always Expected Results: overwrite the file, configure it properly or use another location. In any case a solution that doesn't screw over the other package :P
Same here! I tried putting knetworkconf-4.1.2 in /etc/portage/package.mask but then I couldn't emerge other things since it is a required dependency. Help! :)
Confirming here, The other package that installs this file seems to be app-admin/system-tools-backends
Still have it with 4.1.3. Strange thing is I had the same issue on my ~amd64, and there it seems to have installed fine now. >>> Installing kde-base/knetworkconf-4.1.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/lib/pkgconfig/system-tools-backends.pc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-admin/system-tools-backends-1.4.2-r1 * /usr/lib/pkgconfig/system-tools-backends.pc * * Package 'kde-base/knetworkconf-4.1.3' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message.
*** Bug 266411 has been marked as a duplicate of this bug. ***
I spoken with upstream. Fixed in 4.2.3. Cheers.
