https://bugzilla.novell.com/show_bug.cgi?id=329702#c22
--- Comment #22 from Richard Creighton
As already wrote above, that "FIXED" is related to the fact that the fixed version of yast2-repair was released as online update, so it is available for users who want to run it from installed system. Yes, it doesn't help the users who are not able to boot the system, as stated in early comments.
My point EXACTLY, nothing is fixed. The people that need it the most can't use it
But AFAIK there will be driver update disk released, that should fix even this problem.
Here we are, months after the GM release and that has not happened either so the many people that downloaded the GM release who have a problem and cannot get 10.3 to boot (and thus cannot download the 'fix' either have NO way to fix their problem except to use Knoppix or other repair method. The repair program on the GM release disk IS NOT FIXED, a substitute (remastered disk) was never released, a 'driver update disk' to use your words, was not released, the repair options using released 10.3 GM disks depend on successful installs followed by successful downloads of patches which don't fix underlying problems in the repair modules anyhow, only the API that allows you to call it which doesn't really matter because you have already had to use other means to fix the system in order to be able to do the download and patch in the first place.
And please, do not mix more problems into one report. That doesn't help with finding solutions.
I wasn't the one that characterized this bug report as "yast2-repair module broken", If you wanted to limit it so it was unambiguous then perhaps you could have said 'API calling repair module fails on GM release' or some such, but when you say the yast2-repair module is broken, you are right, it is and it still is even with the patch to enable calling it. The patch only enables calling a still broken module that doesn't do many of the things a repair module is supposed to do. Don't get on my case for managements' bad decisions or for having been the one to characterize this bug as 'yast2-repair module broken'. I only maintain that to say it is resolved is SEMANTICS. To properly resolve 'the proper bug' would have been to implement Comment #1 at a minimum, ideally to simply remaster the GM and the problem would have been moot. -- 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.