When you use openrc-0.4.0 with stable sys-apps/sysvinit-2.86-r10, the system does not physically shutdown nor reboot, because that responsibility has been moved from openrc to sysvinit-2.86-r10. Therefore openrc-0.4.0 should block earlier version of sysvinit as openrc-9999 live version does. (or maybe just notify users that they need to make changes to inittab) Steps to reproduce: emerge =sys-apps/openrc-0.4.0 sys-apps/sysvinit-2.86-r10 poweroff # the system hangs with init saying: no more processes left in this runlevel. See relevant Bug #246502
Well, it currently contains the line !<sys-fs/sysvinit-2.86-r11 so I wonder how you could stay with sysvinit-2.8.6-r10 at all. Maybe this needs adjustment to say !<sys-fs/sysvinit-2.86-r12 as well... Let's see what base-system herd says to this.
Hmm, that's strange, why did portage let me install it without upgrading sysvinit? (that blocker was here from the first revision of openrc-0.4.0.ebuild)
The blocker didn't force me to upgrade as well. Maybe Zack has an idea.
Just for completeness: barcelona:~ # emerge -V Portage 2.2_rc17 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.27.10 x86_64) barcelona:~ # qlist -CIve openrc sys-apps/openrc-0.4.0 barcelona:~ # emerge -pqv =sysvinit-2.86-r10 [ebuild UD] sys-apps/sysvinit-2.86-r10 [2.86-r12] USE="(-ibm) (-selinux) -static" barcelona:~ # This should be blocked by installed sys-apps/openrc-0.4.0, right?
<zmedico> Serkan: blocker says sys-fs/sysvinit instead of sys-apps/sysvinit (wrong category) Thanks, Zack
Hey! We're all blind, the openrc-0.4.0 ebuild blocks sys-fs/sysvinit, but the right package is __sys-apps/sysvinit__! So, Zac, do not panic, it's not a portage bug, rather a typo in ebuild.
OMG, indeed :) In germany this is called "den Wald vor lauter Bäumen nicht sehen" (not seeing the forest because of all the trees). base-system, please fix the typo ;)
I've fixed the blocker in cvs. I'll add a repoman warning for atoms like this that don't match anything.