http://bugzilla.suse.com/show_bug.cgi?id=1089823 http://bugzilla.suse.com/show_bug.cgi?id=1089823#c11 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt@suse.com) | --- Comment #11 from Fabian Vogt <fvogt@suse.com> --- (In reply to Jiri Srain from comment #10)
(In reply to Fabian Vogt from comment #7)
(In reply to Jiri Srain from comment #5)
YaST should IMO show an error if snapper could not be run from whatever reason.
OTOH: There is no need to make a hard dependency on snapper - not all systems want snapshots enabled.
I agree - but a hard dependency in yast2-installation should be fine as normally yast2-installation isn't installed.
Please, no hard dependency. YaST does not require any file system specific tools because the respective filesystem can be used.
Fair enough, but then YaST should not allow those filesystems to be used. If it breaks hard if a tool is not used, it's a hard dependency.
(In reply to Fabian Vogt from comment #6)
OTOH, yast *does* show an error already. So for me this looks fine. Just the KDE Live iso needs fixing.
It's not fine.
The error is *after* the installation.
What does "after installation" mean?
If you look at the linked openQA screenshot, the installation is at 99%, which means except for the snapshot creation it's complete. The system would probably boot fine. -- You are receiving this mail because: You are on the CC list for the bug.