istall of nm fails due to file collision net-misc/networkmanager-0.9.8.2 * checking 214 files for package collisions * 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/bash-completion/nmcli * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-shells/bash-completion-2.1:0::gentoo * /usr/share/bash-completion/nmcli * * Package 'net-misc/networkmanager-0.9.8.2' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. >>> Failed to install net-misc/networkmanager-0.9.8.2, Log file: Reproducible: Always
Well, I think networkmanager should handle this completion instead of bash-completion
Created attachment 350624 [details, diff] modified ebuild: added a rm -f completions/nmcli I absolutely agree with you Pacho, thank you for reassigning) modified ebuild is attached, probably one can improve it by includin the nm version dependent code
*** Bug 473546 has been marked as a duplicate of this bug. ***
Fixed without revision bump.
*** Bug 473646 has been marked as a duplicate of this bug. ***
*** Bug 473874 has been marked as a duplicate of this bug. ***
*** Bug 474344 has been marked as a duplicate of this bug. ***
*** Bug 474526 has been marked as a duplicate of this bug. ***
Still getting the collision here despite syncing every day... From /var/log/emerge.log 1372226433: Started emerge on: Jun 26, 2013 07:00:32 1372226433: *** emerge --keep-going --alphabetical --sync 1372226433: === sync 1372226433: >>> Starting rsync with rsync://91.186.30.235/gentoo-portage 1372226670: === Sync completed with rsync://91.186.30.235/gentoo-portage 1372226711: *** terminating. 1372227189: Started emerge on: Jun 26, 2013 07:13:08 1372227189: *** emerge --ask --update --alphabetical --keep-going --newuse --deep @world 1372227675: >>> emerge (1 of 8) app-text/ps2pkm-1.5_p20130530 to / ... 1372228363: >>> emerge (7 of 8) net-misc/networkmanager-0.9.8.2 to / 1372228363: === (7 of 8) Cleaning (net-misc/networkmanager-0.9.8.2::/usr/portage/net-misc/networkmanager/networkmanager-0.9.8.2.ebuild) 1372228363: === (7 of 8) Compiling/Merging (net-misc/networkmanager-0.9.8.2::/usr/portage/net-misc/networkmanager/networkmanager-0.9.8.2.ebuild) 1372228499: === (7 of 8) Merging (net-misc/networkmanager-0.9.8.2::/usr/portage/net-misc/networkmanager/networkmanager-0.9.8.2.ebuild) 1372228601: *** Finished. Cleaning up... 1372228601: *** exiting unsuccessfully with status '1'. 1372228603: *** terminating. Failing with... net-misc/networkmanager-0.9.8.2 * checking 214 files for package collisions * 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/bash-completion/nmcli * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-shells/bash-completion-2.1:0::gentoo * /usr/share/bash-completion/nmcli * * Package 'net-misc/networkmanager-0.9.8.2' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. There is no mention of nmcli in the ebuild nor can I find the additional 'rm' line to remove nmcli... # grep nmcli /usr/portage/net-misc/networkmanager/.networkmanager-0.9.8.2.ebuild # # grep rm /usr/portage/net-misc/networkmanager/.networkmanager-0.9.8.2.ebuild # Distributed under the terms of the GNU General Public License v2 KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86" ewarn "Was unable to determine your kernel .config" rmdir -v "${ED}/var/run/NetworkManager" || die "rmdir failed" rm -rv "${ED}/etc/init.d" || die "rm failed" rm -f "${old_rules}" || eerror "Failed, please remove ${old_rules} manually" The ebuild at http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/networkmanager/networkmanager-0.9.8.2.ebuild?view=markup doens't appear to remove nmcli either and there is no mention of this bug (472844) in the ChangeLog http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/networkmanager/ChangeLog?view=log How do I use portage to get the patched ebuild if there hasn't been a version bump (and is the fix in the 0.9.8.2 ebuild)?
Yes, you do. This was why I ended up opening Bug 474344. You need to manually re-emerge bash-completion.
(In reply to Dan Goodliffe from comment #10) > Yes, you do. This was why I ended up opening Bug 474344. > You need to manually re-emerge bash-completion. Thanks thats worked fine. It wasn't at all clear to me from this bug post that that was the solution, so your pointer is much appreciated.
*** Bug 475358 has been marked as a duplicate of this bug. ***
Thanks all. I met the same problem while upgrading to net-misc/networkmanager-0.9.8.10, remerge bash-completion just fixed it.
