[Bug 830979] New: sysvinit-init conflicts with aaa_base, with no notice in relnotes package was dropped
https://bugzilla.novell.com/show_bug.cgi?id=830979 https://bugzilla.novell.com/show_bug.cgi?id=830979#c0 Summary: sysvinit-init conflicts with aaa_base, with no notice in relnotes package was dropped Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jra@baylink.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36 I'm well aware that there's been a religious war over sysvinit for a couple of years. I'm well aware that the OS Release Configuration Manager has no interest in the tens of thousands of administrator hours which will be expended by admins who will need to evaluate and switch to an alternative distribution which *does* still run the init system they require, (and which works reliably, though that's another issue I won't litigate here). But -- quite aside from the 6 hours I lost due to the grub2-set-default bug -- *that the trigger was pulled and 12.3 will not allow you to replace systemd with sysvinit at all* *was not documented in the release notes*, and damnit, I looked first. Deprecated in 12.1 and 12.2, not mentioned in 12.3 at all. And given the size of the R-war over this, I can only attribute this to "we don't care, we don't have to; we're The Phone Company". That's my cue to jump out of the airplane. I'll be reinstalling *again* on this system, with 12.2, whilst I search for a permanent solution, which will involve dropping a SUSE distribution chain I've been with since 8.3. Way to go, guys. Way to go. Reproducible: Always Steps to Reproduce: 1. 2. 3. This is a hard, permanent, commercial downcheck for me; I will stop using the distribution, and advise everyone else of my interpretation of the reasons for the situation, and that they should avoid it as well. I see that you've removed Blocker as a severity. Owel. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c1
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c2
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c
Karl Eichwalder
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c3
--- Comment #3 from Jay Ashworth
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c4
--- Comment #4 from Jay Ashworth
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c5
--- Comment #5 from Karl Eichwalder
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c6
--- Comment #6 from Jay Ashworth
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c7
Karl Eichwalder
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c8
--- Comment #8 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=830979
https://bugzilla.novell.com/show_bug.cgi?id=830979#c9
--- Comment #9 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com