http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c1 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt@suse.com Resolution|--- |WONTFIX --- Comment #1 from Stephan Kulow --- 10:30 < DimStar> the current KDE live disk size is: 996147200 - there is not enough space for the full dict -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c20 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #20 from Ancor Gonzalez Sosa --- The main problem here is that the YaST code is conceived to work only on the inst-sys. I mean, it uses the so-called installation extensions to load dict-full dynamically. See this code: https://github.com/yast/yast-users/blob/29d0c407f6d15a89da7cfa856c9f9e1c65db... But that results in the following errors in the logs: [Ruby] modules/InstExtensionImage.rb:386 Calling: extend 'cracklib-dict-full.rpm' [bash] ShellCommand.cc(shellcommand):78 sh: extend: command not found [Ruby] modules/InstExtensionImage.rb:388 Returned: $["exit":127, "stderr":"sh: extend: command not found\n", "stdout":""] [Ruby] modules/InstExtensionImage.rb:392 'extend' failed! [Ruby] users/local_password.rb:97 loading cracklib failed, not used for pw check[Ruby] modules/InstExtensionImage.rb:418 Package cracklib-dict-full.rpm wasn't integrated We would need either to adapt YaST to recognize the situation and not try to use the installer extensions (i.e. using the 'extend' command) or to provide 'extend' in the live system with a different behavior when compared to the inst-sys (e.g. checking if something is there, instead of trying to load it temporarily. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c22 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ancor@suse.com) --- Comment #22 from Fabian Vogt --- (In reply to Fabian Vogt from comment #21)

(In reply to Ancor Gonzalez Sosa from comment #20)

...

The main problem here is that the YaST code is conceived to work only on the inst-sys. I mean, it uses the so-called installation extensions to load dict-full dynamically. See this code:

https://github.com/yast/yast-users/blob/ 29d0c407f6d15a89da7cfa856c9f9e1c65dbeef0/src/modules/UsersSimple.pm#L973

Thanks for the analysis!

...

But that results in the following errors in the logs:

[Ruby] modules/InstExtensionImage.rb:386 Calling: extend 'cracklib-dict-full.rpm' [bash] ShellCommand.cc(shellcommand):78 sh: extend: command not found [Ruby] modules/InstExtensionImage.rb:388 Returned: $["exit":127, "stderr":"sh: extend: command not found\n", "stdout":""] [Ruby] modules/InstExtensionImage.rb:392 'extend' failed! [Ruby] users/local_password.rb:97 loading cracklib failed, not used for pw check[Ruby] modules/InstExtensionImage.rb:418 Package cracklib-dict-full.rpm wasn't integrated

We would need either to adapt YaST to recognize the situation and not try to use the installer extensions (i.e. using the 'extend' command) or to provide 'extend' in the live system with a different behavior when compared to the inst-sys (e.g. checking if something is there, instead of trying to load it temporarily.

I guess using this as /usr/sbin/extend:

#!/bin/bash rpm -q ${1%%.rpm} >/dev/null >&1 || zypper --non-interactive in ${1%%.rpm}

would work as a workaround. Maybe it's even a proper fix, I'm not sure how this behaves in certain situations. I'll try to give this a try in live-net-installer.

I tried it - it works if the package is already installed. Otherwise zypper aborts because YaST currently holds the lock. Any idea? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c24 --- Comment #24 from Fabian Vogt --- (In reply to Ancor Gonzalez Sosa from comment #23)

(In reply to Fabian Vogt from comment #22)

...

...

I guess using this as /usr/sbin/extend:

#!/bin/bash rpm -q ${1%%.rpm} >/dev/null >&1 || zypper --non-interactive in ${1%%.rpm}

would work as a workaround. Maybe it's even a proper fix, I'm not sure how this behaves in certain situations. I'll try to give this a try in live-net-installer.

I tried it - it works if the package is already installed. Otherwise zypper aborts because YaST currently holds the lock. Any idea?

To be honest, I was expecting the fake extend to simply return 0 if the package is already there and another exit code otherwise (basically the first half of your script). That should be enough as a workaround for the live installer case. I don't think is worth it (or even realistic) to actually install the package if it's missing.

If you think that it's not that important to implement that, I can submit the first part for now. Packages can be installed as usual on live media (with or without persistence), so there's no technical reason not to enable this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c27 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #27 from Dominique Leuenberger --- (In reply to Fabian Vogt from comment #26)

openQA reports that the softfail is gone -> fixed!

Verification screenshot: https://openqa.opensuse.org/tests/671631#step/user_settings/3 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013206 http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c32 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #32 from Fabian Vogt --- It's really fixed everywhere now. -- You are receiving this mail because: You are on the CC list for the bug.