At the time of writing, sys-apps/policycoreutils-2.7_rc1 (from now on "policycoreutils") has a PDEPEND on sys-apps/selinux-python. This is needed because some of the logic previously part of policycoreutils is now moved into a separate package. However, when trying to upgrade policycoreutils, the used dependency tree fails as it tries to install sys-apps/selinux-python-2.7_rc1 (from now on "selinux-python") first, which causes file collisions. This is to be expected, as PDEPEND does not guarantee post-deployment installation. To accomplish that, a blocker needs to be put in place, so that selinux-python explicitly mentions it cannot be installed alongside an older policycoreutils. Small remark: Portage seems to use a different ordering based on the used command: ~# emerge -u policycoreutils -p ~# emerge -u policycoreutils -pt In the first situation, it tried to install selinux-python first, while in the second one it tried to upgrade policycoreutils first.
Blocker put in place See https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b169bf26e1cde951a1b123d4a390a38694f18971
Created attachment 508780 [details] build.log The issue seems not fixed, I just hit this when upgrading a system
2.6 has been dropped from the tree half a year ago, no need to worry about minor migration issues anymore.
