http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c20 --- Comment #20 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Fabian Vogt from comment #19)

...

4) But instead of fixing the buggy environment (that was the premise, "difference in environments should be neglegible, anything else is a bug in the environment") we end up with a bunch of bug reports about thing we have to adapt in the YaST side for it to work in this new environment. That was not the deal.

First of all, let me clarify something. I talked about "buggy environment" as a direct application of your own sentence: "anything else is a bug in the environment". As far as I understood that sentence, it means that if something works in the normal official installation but it does not work in the live media, it ought to be considered a bug in the live media itself, not in YaST.

Please tell me which bugs in the environment you're talking about here, to my knowledge there aren't any open ones.

Let's perform a very quick search to find some bugs about something being broken in the live media, although it works in the normal int-sys (there are many more examples... including several ones that has been fixed in the YaST side): - bug#1151291 - bug#1151148 - bug#1089823 - bug#1059298 - bug#1155516 - bug#1155687 - bug#1157686 None of those are a problem when the installer runs in the official int-sys, which is the environment for which we develop and test the installer. The problems only arise when executed in that different environment that is the live media. That's why I dared to call them "bugs in the environment" as a direct application of the rule above. All those bugs are currently assigned to yast2-maintainers. So you can say they are not bugs in the environment, but things the YaST Team should fix by modifying YaST. But, as said, that was not the deal. -- You are receiving this mail because: You are on the CC list for the bug.