Bug 343650

I apologize. I inadvertently left out the error message which is "An error occurred during the installation". That particular message doesn't leave much to the imagination, does it?
 

*** This bug has been marked as a duplicate of bug 329702 ***

Please excuse my ignorance Martin but I fail to see a resolution for removable media recovery in bug 329702 for 10.3 users. 329702 deals with "yast2-repair module broken" and although booting to "Repair Installed System" is mentioned in conjunction, there is currently NO solution and 329702 has a Status/Resolution of RESOLVED/FIXED. Sorry, the problem I reported is by far from being RESOLVED/FIXED. Show me a way or please reopen my bug. I consider your marking this bug a duplicate an easy way out for someone! Period! 

Hi Mike, 
first of all, thank you for your bugreport.

(In reply to comment #3 from Mike Wells)
> Please excuse my ignorance Martin but I fail to see a resolution for removable
> media recovery in bug 329702 for 10.3 users. 329702 deals with "yast2-repair
> module broken" and although booting to "Repair Installed System" is mentioned
> in conjunction, there is currently NO solution and 329702 has a

Yes, your problem is not solved but its impossible to solve it (its explained in bug 329702 why), because it is on the media which was already released (i.e. the CD you have burned and/or bought). We would need to release another set of medias, which is impossible :-(

When a bug is FIXED it doesn't necessarily mean it will end-up in the current release (10.3 in this case). Even if it would be possible to fix this bug using an online update, it still doesn't mean that each FIXED bug is released as an online update. Some of the bugs will be fixed in the next version of openSUSE. This bug will be definitely fixed in the next openSUSE release (another solution how to fix this are in bug #329702). 

Broken yast2 repair is the root cause why the repair system doesn't work. If you will check bug #329702 carefully, you will see a lot of bugs marked as duplicate. Many of them are exactly like yours.


> Status/Resolution of RESOLVED/FIXED. Sorry, the problem I reported is by far
> from being RESOLVED/FIXED. Show me a way or please reopen my bug. I consider
> your marking this bug a duplicate an easy way out for someone! Period! 

Believe me its not! Thats the last thing I would do. 

I hope this comment makes sense and clarifies the situation.

Thank you very much Martin for taking the time out for the verbose explanation. That does not come very often and I for one sincerely appreciate it.

I fully understood that there was no way that this could be repaired in the current release and I've been around long enough to have my ducks in a row when it comes to disaster recovery (well, most of the time anyway...lol).

In all honesty it can almost be construed as disrespect to the openSUSE community (I being a long time member of that) to let this kind of situation even occur, when knowing full well that it had existed since beta. We would rather have the GM delayed a week or so in order that we get a product that is "whole" instead of one that met schedule but is full of holes where there should not be any.

Quite frankly, these "little" things add up for us out "here". We haven't had a "working" 3.5"/1.44MB floppy since 9.3 and 10.3 is by far the worst release that I have seen (been with you guys since 9.1) for CUPS/YaST/HP/HPLIP printing. I think that you can understand what happens to our frustration levels when the R&D team is busy cramming essentially unusable KDE4 features in the 10.3 release but totally ignore the fundamental things that we have come to expect and require since the dawn of the PC.

I hope you can now better understand and perhaps see our side a little more clearly. Remembering too, that "we" do not have anywhere near the knowledge that you "insiders" have with respect to this OS. And to be perfectly blunt, the overall documentation for this magnitude of a system is sorely lacking and that has always been the case. I wish mind reading was free so we could know what you guys know - but it is not.

Thanks again Martin, you will be one of the few that I will remember!