Bug 725142 - Applications using rubygem-thin can't use ruby gem, fails to load modules
Summary: Applications using rubygem-thin can't use ruby gem, fails to load modules
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-thin
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Chris Lalancette
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-23 07:48 UTC by Shawn Starr
Modified: 2011-07-25 15:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-25 08:34:19 UTC
Type: ---


Attachments (Terms of Use)

Description Shawn Starr 2011-07-23 07:48:13 UTC
Description of problem:
Unable to load the thin rubygem modules

Version-Release number of selected component (if applicable):
thin-1.2.11

How reproducible:
100%

Steps to Reproduce:

ruby -e 'require "rubygems" ;
 require "thin"'
 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
 `gem_original_require': no such file to load -- /usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin_parser (LoadError)
     from
 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
 `require'
     from
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin.rb:47
     from
 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:59:in `gem_original_require'
     from
 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:59:in `require'
     from -e:1
  
Actual results:
Fails to load DSO plugin for thin

Expected results:
Loads, no stack trace thrown.

Please note: This RPM is dependent on packaging OpenNebula 3.0 for Fedora SIG, without it being fixed, this blocks any further release.

Comment 1 Shawn Starr 2011-07-23 07:48:41 UTC
sorry Fedora Cloud SIG

Comment 2 Chris Lalancette 2011-07-25 08:34:19 UTC
This should be fixed in rawhide now.  Feel free to re-open if you are still running into problems.

Comment 3 Shawn Starr 2011-07-25 15:26:25 UTC
Confirmed fixed for me.


Note You need to log in before you can comment on or make changes to this bug.