http://bugzilla.opensuse.org/show_bug.cgi?id=1013206
http://bugzilla.opensuse.org/show_bug.cgi?id=1013206#c22
Fabian Vogt
(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.