I get the message: "sys-apps/portage-2.1.4_rc1 (is blocking app-shells/bash-3.2_p33" when trying to update either bash or portage. I don't know how to resolve this conflict.
This is not a support forum...
*** Bug 206188 has been marked as a duplicate of this bug. ***
Although I opened 206188 as an enhancement request, it really is a bug. Portage should not block ebuilds without a giving the user some explanation. Please reopen that request.
This is no portage bug; we have changelogs for similar stuff.
Please just pass it onto the portage team and let them decide what to do with it.
(In reply to comment #5)
> Please just pass it onto the portage team and let them decide what to do with
Like, exactly what? Kindly review Bug 190128; no it doesn't work, the blocker is there for a reason so live with it.
(In reply to comment #1)
> This is not a support forum...
I read through those and more. From what I could gather from the docs, this was a circular block; from the Portage docs:
"It is also possible that two packages that are yet to be installed are blocking each other. In this rare case, you should find out why you need to install both. In most cases you can do with one of the packages alone. If not, please file a bug on Gentoo's bugtracking system."
I played around with some today and no, portage is at fault here. It's lying about what's doing the blocking. It claims that portage-2.1.4_rc1 is doing the blocking. But guess what? That version doesn't even exist. It should really be saying the presently installed version is blocking, which is older. And even then it's not really blocking. Because all it has to do is install the new version as a dependency. Initially, it couldn't do this because on my system, the correct version is masked. But even when it wasn't, it just sat there claiming the non-existent version was blocking it. Definitely portage is dumb. So this is something that can be "fixed".
If you are mixing latest ~arch bash with stable portage, kindly either downgrade you bash or stick portage to package.keywords (or better yet stick with stable only if you don't know what you are doing).
Any further comment here documenting a failure to read basic portage documentation (including the link provided by portage itself on hitting a blocker) will result in restricting this bug to prevent further noise in my mailbox.
Exactly same message hit me today on one of the rarely touched systems. It's easily fixed now by emerging by hand all the unmet portage dependencies, then emerging portage with --nodeps, then emerging the bash.