These are the packages that would be merged, in order: Calculating dependencies... done! [blocks B ] <app-arch/rpm-4.2.1 (is blocking dev-libs/beecrypt-3.1.0-r2) [ebuild N ] dev-libs/beecrypt-3.1.0-r2 USE="python" 441 kB [ebuild U ] app-arch/rpm-4.4.1-r1 [4.2] USE="nls python -doc" 11,227 kB portage-2.1.1_pre1-r2 Now I know that it is the old version of rpm that is blocking beecrypt, but I would consider this as a bug. A package should not block a package if it is going to be unmerged in the same emerge, at least thats my opinion. This caused me headaches until somebody told me it was the version not the whole package that blocks beecrypt.
*** This bug has been marked as a duplicate of 79606 ***