* Detected file collision(s): * * /usr/share/bash-completion/completions/mc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-fs/mc-0_pre20171014:0::gentoo * /usr/share/bash-completion/completions/mc * * Package 'app-shells/bash-completion-2.7-r1' NOT merged due to file ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-plasma_test_20171129-200748 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python3.5 (fallback) [4] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-shells/bash-completion [ebuild N ] app-shells/bash-completion-2.7-r1 USE="{-test}"
Created attachment 508148 [details] emerge-info.txt
Created attachment 508150 [details] app-shells:bash-completion-2.7-r1:20171204-101913.log
Created attachment 508152 [details] emerge-history.txt
Created attachment 508154 [details] etc.portage.tbz2
Created attachment 508156 [details] logs.tbz2
That said, I don't really understand how a developer could consider it a good idea to create a package that collides with Midnight Commander. That's a recipe for a completely useless package.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b0d2ac11db06d5963b0ca309b1e27478adb85bed commit b0d2ac11db06d5963b0ca309b1e27478adb85bed Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2018-01-05 09:41:55 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-01-05 09:43:45 +0000 app-shells/bash-completion: Block net-fs/mc due to file collision Closes: https://bugs.gentoo.org/639828 ...{bash-completion-2.7-r1.ebuild => bash-completion-2.7-r2.ebuild} | 6 ++++-- app-shells/bash-completion/bash-completion-9999.ebuild | 6 ++++-- 2 files changed, 8 insertions(+), 4 deletions(-)
I just ran into this (frustrating) collision problem today. "What were they thinking?" indeed. I would propose renaming 'net-fs/mc' ==> 'net-fs/mc3' It is sort of a play off it being a S3 compatible client. FWIW, that is what I did when I hijacked the ebuild into my local repo.
