Emerging openrc-0.35 fails due to file collisions with bash completion scripts from app-shells/gentoo-bashcomp-20140911: Reproducible: Always Steps to Reproduce: 1. emerge =app-shells/gentoo-bashcomp-20140911 2. emerge =sys-app/openrc-0.35 Actual Results: * Messages for package sys-apps/openrc-0.35: * 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 https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And 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/completions/rc-update * /usr/share/bash-completion/completions/rc-status * /usr/share/bash-completion/completions/rc-service * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-shells/gentoo-bashcomp-20140911:0::gentoo * /usr/share/bash-completion/completions/rc-service * /usr/share/bash-completion/completions/rc-status * /usr/share/bash-completion/completions/rc-update * * Package 'sys-apps/openrc-0.35' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. * * The following package has failed to build, install, or execute postinst: * * (sys-apps/openrc-0.35:0/0::gentoo, ebuild scheduled for merge), Log file: * '/tmp/portage/sys-apps/openrc-0.35/temp/build.log' * Expected Results: A successful emerge of openrc.
confirm
Same problem here.
My understanding after chatting with devs about it is that gentoo-bashcomp has been broken for a long time with bash completion 2.1, so at this point the best I can do is block gentoo-bashcomp with the new OpenRC.
Why can't these specific files be removed from the app-shells/bash-comp package as the sys-apps/openrc package already has the more up to date ones? It would solve the issue as long as both packages are updated at the same time and correct order, or am I just missing something?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9d1bfb6699834cb9b1ec25624186a53d288198f commit a9d1bfb6699834cb9b1ec25624186a53d288198f Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-03-02 01:04:58 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-03-02 01:06:03 +0000 app-shells/gentoo-bashcomp: revbump to 20140911-r1 (bug 649144) Remove rc-{service,status,update} completions in order to solve a file collision with openrc-0.35.1. Bug: https://bugs.gentoo.org/649144 Package-Manager: Portage-2.3.24, Repoman-2.3.6 .../gentoo-bashcomp-20140911-r1.ebuild | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+)}
@shell-tools: For the record, I thought about making this change, but it wasn't clear that I had permission to touch the ebuild.
I bumped gentoo-bashcomp to 20180302 which makes this official upstream. Thanks, William
