From recent discussions on the different openSUSE lists about systemd it looks
https://bugzilla.novell.com/show_bug.cgi?id=725917 https://bugzilla.novell.com/show_bug.cgi?id=725917#c18 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #18 from Lars Müller <lmuelle@suse.com> 2011-11-12 18:19:05 CET --- I consider blacklisting - zypper lock or from inside the YaST UI - an approach we should not recommend to our users. I expect sysvinit to vanish completely in two or three releases as soon as the systemd stack settles more and more. Guess we suggest to lock systemd-sysvinit. In two years when the users upgrade their systems they no longer have the motivation to lock the package in mind. Then libzypp will run into an unresolvable situation. Therefore I strongly vote against suggesting a lock of the systemd-sysvinit package. Adding some additional magic to libzypp to handle all this causes extra work too and would be yet another level of indirection causing at the end more and more hassle. Over all the decision - as much as I don't like it - is the right approach. We have to focus on one technical solution and make this solution a nicely and smooth working one. That's what Frederic is working hard on. It's nor our obligation to help him as much as possible to make systemd smoothly fly with the next release. like the systemd documentation is one major piece which needs our attention in the recent future. @Ruediger + Klaas: Feel free to close this issue as resolved/worksforme if non of you doesn't have a more elegant solution at hand. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.