On Mon, 23 Sep 2013 21:41:01 +0200 Alejandro Bonilla <abonilla@linuxwireless.org> wrote:
On Mon, Sep 23, 2013 at 10:26 AM, Ladislav Slezak <lslezak@suse.cz> wrote:
Dne 22.9.2013 20:45, Alejandro Bonilla napsal(a):
Hi,
On Sun, Sep 22, 2013 at 5:32 PM, Stephan Kulow <coolo@suse.de> wrote:
Am 20.09.2013 20:58, schrieb Alejandro Bonilla:
Hi,
I've upgraded from 12.3 to 13.1 but unfortunately, yast won't load. It looks like the culprit is
2013-09-20 14:05:03 <3> e6510.site(15413) [Y2Ruby] binary/YRuby.cc(callClient):235 cannot require yast:cannot load such file -- fast_gettext at /usr/lib64/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
Do we have any information on the new requirements for yast?
Thanks, Al
What does rpm -V yast2-ruby-bindings-3.0.0 output?
nothing.
Strange,
# rpm -q --requires yast2-ruby-bindings-3.0.0 ... ruby rubygem-fast_gettext
Could you check whether rubygem-fast_gettext is installed correctly?>
rpm -V gives nothing zypper in -f rubygem-fast_gettext reinstalled it fine
Repository: Main Repository (OSS) Name: rubygem-fast_gettext Version: 0.7.1-1.2 Arch: x86_64 Vendor: openSUSE Installed: Yes Status: up-to-date still the same issue
2013-09-23 21:33:51 <1> e6510.site(5795) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'menu' 'ncurses' 2013-09-23 21:33:51 <1> e6510.site(5795) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for "" 2013-09-23 21:33:51 <1> e6510.site(5795) [liby2] genericfrontend.cc(main):764 YAST_IS_RUNNING is yes 2013-09-23 21:33:51 <3> e6510.site(5795) [Y2Ruby] binary/YRuby.cc(callClient):235 cannot require yast:cannot load such file -- fast_gettext at /usr/lib64/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require' 2013-09-23 21:33:51 <1> e6510.site(5795) [liby2] genericfrontend.cc(main):780 Finished YaST2 component 'y2base' 2013-09-23 21:33:51 <1> e6510.site(5795) [liby2] genericfrontend.cc(main):785 Exiting with client return value 'nil'
/usr/lib64/ruby/2.0.0/rubygems/core_ext/kernel_require.rb exists... and the permissions dont make a difference
yast2 does "work" and I can see the different modules but once I click on them, I see the same error...
:| what other clues?
OK, wild quest, there was problem with loading rubygems when you use more recent ruby-bindings, but it should affect only ruby-bindings 3.0.1 and 3.0.2 and is fixed in 3.0.3. So question is if you don't try own yast2-ruby-bindings. If you try the latest ruby-bindings from YaST:Head repo does it help? Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org