Created attachment 555102 [details] Build log Emerging dev-lang/rust-1.30.0 fails due to file collision as described in the following QA notice: * 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/zsh/site-functions/_cargo * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-util/cargo-0.30.0:0::gentoo * /usr/share/zsh/site-functions/_cargo * * Package 'dev-lang/rust-1.30.1' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
Created attachment 555104 [details] emerge --info
Correct version of rust is 1.30.1, there was a typo in the original post.
I have the smae issue.
Deleting cargo can be used as a workaround.
You can just unmerge dev-util/cargo now because it is provided by dev-lang/rust
Soft blockers don't work when not in RDEPEND.
im experiencing this as well. so we dont need cargo anymore and can just emerge -C it or am i misunderstanding the workaround?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=107cec48583866aea34a98178763cabb7eb74606 commit 107cec48583866aea34a98178763cabb7eb74606 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-11-15 01:12:10 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-11-15 01:19:53 +0000 dev-lang/rust-bin: move soft blockers to RDEPEND Closes: https://bugs.gentoo.org/671150 Package-Manager: Portage-2.3.51, Repoman-2.3.12 RepoMan-Options: --force Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> ...bin-1.29.1.ebuild => rust-bin-1.29.1-r1.ebuild} | 23 +++++++++++----------- ...bin-1.29.2.ebuild => rust-bin-1.29.2-r1.ebuild} | 23 +++++++++++----------- ...bin-1.30.1.ebuild => rust-bin-1.30.1-r1.ebuild} | 17 ++++++++-------- 3 files changed, 30 insertions(+), 33 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=76023b2a81ae1927ec5857256fb65d1bec61c509 commit 76023b2a81ae1927ec5857256fb65d1bec61c509 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-11-15 00:50:27 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-11-15 01:19:51 +0000 dev-lang/rust: move soft blockers to RDEPEND Closes: https://bugs.gentoo.org/671150 Package-Manager: Portage-2.3.51, Repoman-2.3.12 RepoMan-Options: --force Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> dev-lang/rust/{rust-1.29.1.ebuild => rust-1.29.1-r1.ebuild} | 10 +++++----- dev-lang/rust/{rust-1.29.2.ebuild => rust-1.29.2-r1.ebuild} | 10 +++++----- dev-lang/rust/{rust-1.30.1.ebuild => rust-1.30.1-r1.ebuild} | 10 +++++----- 3 files changed, 15 insertions(+), 15 deletions(-)
Sorry about that, and thanks for cleaning up after me. I remember wondering about how this should work, but was in a bit too much of a hurry to get it done yesterday. :(
*** Bug 664286 has been marked as a duplicate of this bug. ***
(In reply to jeremy mills from comment #7) > im experiencing this as well. so we dont need cargo anymore and can just > emerge -C it or am i misunderstanding the workaround? Cargo is emerged again as a dependency of thunderbird or firefox.
Juergen/Jeremy: just to make this clear, previously you could either install dev-util/cargo separately (and this was the first way of installing cargo, so many people have it installed) or as part of dev-lang/rust or dev-lang/rust-bin. For this latest upgraded I've not upgraded the dev-util/cargo package, instead mandating that everyone get their cargo from dev-lang/rust or dev-lang/rust-bin. So it should still be installed, but in some cases you have to rerun `sudo eselect rust set rust-1.30.1` (or `sudo eselect rust set rust-bin-1.30.1`) to make it work again (see bug 671182).
