http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c18 --- Comment #18 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Lukas Ocilka from comment #17)
(In reply to Fabian Vogt from comment #11)
There was no bugzila nr or FATE nr in that submission so I guess no request existed.
Ancor, do you have some, PLS?
I can't find any. My memory is faulty, but I'm pretty sure it was not my idea, just something I submitted because somebody asked whether it was possible. But I cannot find the original conversation.
No dropping should be necessary - the difference in environments should be neglegible, anything else is a bug in the environment.
I don't follow the reasoning here. 1) We develop the installer for a known and controlled environment (the standard int-sys). 2) Then you introduce a new environment (the live image) claiming that things should work and, if not, it's a bug in the environment. 3) Then turns out that, although the YaST team has been trying to help when possible and reasonable, the whole thing actually does not work as smooth as expected. 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. As a cherry on top, now the installation and upgrade process from the live image seems to be considered critical to release a new Tumbleweed snapshot. So something that was on our side "hey, let's support that guy in his brave crazy idea" has step by step become "it's our responsibility and it's urgent when it breaks". -- You are receiving this mail because: You are on the CC list for the bug.