http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c14 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com, | |locilka@suse.com Flags| |needinfo?(jsrain@suse.com), | |needinfo?(fvogt@suse.com) --- Comment #14 from Lukas Ocilka <locilka@suse.com> --- (In reply to Fabian Vogt from comment #11)

(In reply to Stefan Hundhammer from comment #10)

...

IIRC we had a live installer many, many years ago, and then it was dropped because there was a neverending flood of problems. How exactly was that thing revived?

This has absolutely nothing to do with "yast2-live-installation". This is running the plain YaST installation, from a live system instead of installation-images.

So, Fabian, who took the decision to just use the Installation/Upgrade tool and used that in a completely unsupported scenario? Who takes the responsibility for bugs that logically have to happen just because the well-defined installation environment is silently replaced with a running system? Yes, this is open-source, so we definitely support when someone takes the code and uses it somewhere else. But is a bit problematic to take and fix all bugs that happen because of that. The team is not inflatable, we seem to have far more important tasks to do. Is this the new major way how to install openSUSE? And what do we drop instead? Jiri, do we have anything about supporting this scenario? We usually have a FATE/JIRA, some maintenance plan, ... is there anything? Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.