display-manager-init is conflicting with my sysvinit sys-apps/sysvinit is soft blocking gui-libs/display-manager-init which I need for my sys-apps/openrc. I hacked the ebuild to get rid of that dependency, it works fine.
You've truncated the output. It only blocks certain older versions of sysvinit: >!<=sys-apps/sysvinit-2.98 Why can't you upgrade sysvinit?
Woops! I have ptsd upgrading low-level stuff, and incorrectly assumed that xorg-server was trying to do disrespectfully coerce me to use some new stuff (eg. all this new stuff around "wayland" and "systemd") Anywho, why didn't portage simply upgrade sysvinit for me?
(In reply to Dennis Nezic from comment #2) > Woops! I have ptsd upgrading low-level stuff, and incorrectly assumed that > xorg-server was trying to do disrespectfully coerce me to use some new stuff > (eg. all this new stuff around "wayland" and "systemd") I don't remember the exact reason for the blocker but I can dig it up if you want (it'd involve going back and looking at the old xdm package or whatever it was). > > Anywho, why didn't portage simply upgrade sysvinit for me? I think it depends on what command you ran :) When there's blockers involved, Portage is just saying "I can't proceed", rather than "I know what we could do, but you haven't told me to". I think it's pretty much https://wiki.gentoo.org/wiki/Project:Portage/FAQ#Why_is_there_a_dependency_conflict_when_I_attempt_to_upgrade_a_single_package.3F.
