| Summary: | ruby-gettext not found in default ruby module path | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Shyam Mani (RETIRED) <fox2mike> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | john, ruby |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | strace output when you run alexandria | ||
|
Description
Shyam Mani (RETIRED)
2009-01-08 08:10:28 UTC
Also, it could be an issue with ruby-gettext, I'm not sure. Since all the other .rb's are in /usr/lib/ruby/site_ruby/1.8/ but gettext isn't. Created attachment 177740 [details]
strace output when you run alexandria
strace output.
Running rsync -avP /usr/lib/ruby/gems/1.8/gems/gettext-1.93.0/lib/ /usr/lib/ruby/site_ruby/1.8/ fixes the issue and alexandria is able to start. So is it ruby-gettext that's not putting it's stuff in the right place. CC'ing the ruby folks as well. Reassigning to maintainer. Re-assigning to Ruby herd as this does not seem to be an Alexandria bug and my knowledge of Ruby isn't good enough to progress any further. I notice that in your strace output there is no reference to gems, but when I strace alexandria on my system the first thing ruby does is read /usr/lib64/ruby/site_ruby/auto_gem.rb which I think sets up the required state for "require 'gettext'" to find gettext.rb in /usr/lib/ruby/gems/1.8/gems/gettext-1.93.0/lib/. (In reply to comment #6) > I notice that in your strace output there is no reference to gems, but when I > strace alexandria on my system the first thing ruby does is read > /usr/lib64/ruby/site_ruby/auto_gem.rb which I think sets up the required state > for "require 'gettext'" to find gettext.rb in > /usr/lib/ruby/gems/1.8/gems/gettext-1.93.0/lib/. ruby-gettext is installed where it should belong, you just need to require "rubygems" (which we have handled in auto_gem.rb) before requiring a gem. It's a restriction that ruby fixes only with 1.9. Shyam: I suspect that the auto_gem magic is broken on your machine. Please make sure that the environment variable RUBYOPT is set to "-rauto_gem". There should be a file in /etc/env.d taking care of that. Alternatively, you could patch /usr/bin/alexandria to require rubygems before everything else (either by having -rubygems added to the shebang or doing 'require "rubygems"') explicitly or have upstream do that. Given that from what I know other distros or platforms don't have the magic we do, it should be there anyway. (In reply to comment #7) > Shyam: I suspect that the auto_gem magic is broken on your machine. Please make > sure that the environment variable RUBYOPT is set to "-rauto_gem". There should > be a file in /etc/env.d taking care of that. # echo $RUBYOPT -rauto_gem So that's taken care of. As is env.d... # cat /etc/env.d/10rubygems RUBYOPT="-rauto_gem" > Alternatively, you could patch /usr/bin/alexandria to require rubygems before > everything else (either by having -rubygems added to the shebang or doing > 'require "rubygems"') explicitly or have upstream do that. Given that from what > I know other distros or platforms don't have the magic we do, it should be > there anyway. > I'd be fine with patching stuff here, but the point is a normal end user might wonder why Alexandria won't even run...so I guess that needs to be taken care of (In reply to comment #8) > I'd be fine with patching stuff here, but the point is a normal end user might > wonder why Alexandria won't even run...so I guess that needs to be taken care > of Mhhhh. With the settings in order it _really_ should work. I think we should do some more elaborate debugging before starting to patch it in, as it just seems to be you who has this issue. ;) Feel free to poke me on IRC (in #gentoo-ruby maybe) sometime and we'll check the whole magic. |
