Consider the following: I have installed old sysvinit & util-linux. New sysvinit blocks old util-linux, and new util-linux blocks old sysvinit; so I have to update both in pair. Now, portage builds and install new sysvinit; my system is left without sulogin. Then portage tries to build util-linux and fails. My system is still left without sulogin until I downgrade sysvinit. I believe it would be really more friendly if portage built the both packages blocking each other but delayed the merge until both are built. This way, the failure would occur before old sysvinit is unmerged, and leave me with working sulogin.
I'm having similar problems, "<sys-apps/util-linux-2.22.1" is blocking sys-fs/ntfs3g-2012.1.15-r2.. so firstly i tried to emerge a newer version of util-linux (~ 2.22.1), but this version is blocked by: "<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.1) Total: 1 package (1 upgrade, 1 uninstall), Size of downloads: 3,120 kB Conflict: 2 blocks (1 unsatisfied). However, if i want to emerge this testing version of sysvinit, it is blocked by util-linux: <sys-apps/util-linux-2.22 ("<sys-apps/util-linux-2.22" is blocking sys-apps/sysvinit-2.88-r4) This is an enhancement, should it be filed as a bug as well?
(In reply to comment #1) > This is an enhancement, should it be filed as a bug as well? No, this bug is enough. Also, if blockers don't solve automatically then it typically means you have a "hard" !!atom blocker, which may be automatically solved if we implement bug 250286.
