There are circular dependencies between them: (sys-apps/systemd-207-r2::gentoo, ebuild scheduled for merge) depends on (sys-apps/gentoo-systemd-integration-2::gentoo, ebuild scheduled for merge) (runtime) (sys-apps/systemd-207-r2::gentoo, ebuild scheduled for merge) (runtime)
+ 26 Sep 2013; Mike Gilbert <floppym@gentoo.org> systemd-204-r1.ebuild, + systemd-207-r2.ebuild, systemd-9999-r1.ebuild: + Move gentoo-systemd-integration to PDEPEND, bug 486112. +
Hmm but this shouldn't be necessary... we should be able to handle it via blockers, at worst.
How would blockers help anything here? I assume this is basically an issue for a fresh systemd install, where we pull in both systemd and gentoo-systemd-integration, and portage doesn't know which to install first.
Well, since both are just RDEPENDs... shouldn't portage install them in any order?
Oh, yes. Reopening since I apparently have no clue as the the issue here.
Looks like exactly same as http://bugs.gentoo.org/show_bug.cgi?id=480328#c7
Created attachment 359586 [details] emerge --info output
mgorny's assumption about how circular deps in RDEPEND just seems to be incorrect. gentoo-systemd-integration was moved to PDEPEND some time ago, so I'm closing this again.