Description of problem:
`gem which $gem_with_so_ext` reports `ERROR: Can't find ruby library file
or shared library $gem_with_so_ext`, although `gem list | grep
$gem_with_so_ext` shows it is installed properly.
Version-Release number of selected component (if applicable):
100% -- I used `xmlparser` and `slop` for testing, other should behave
Steps to Reproduce:
1. pick a gem with native extension in %gem_extdir_mri
2. gem which $picked_gem
3. ERROR: Can't find ruby library file or shared library $picked_gem
4. pick a gem which is written in pure Ruby (no native so-extension)
5. gem which $pure_ruby_gem
6. Shows install-path correctly
Should work as expected or with "pure" Ruby gems.
rubygems on Fedora 19 might be affected as well (didn't test).
F-19 also affected
For F-20, locally modified
Please note that there might be some interesting patch available in RubyGems 2.2, which would fix this issue. On the other hand, there were more changes, so it might be hard to backport.
rubygems-2.1.11-115.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rubygems-2.1.11-115.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
I will modify F-19 rubygems this weekend (perhaps)
rubygems-2.1.11-115.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
rubygems-2.0.14-113.fc19 has been submitted as an update for Fedora 19.
rubygems-2.0.14-113.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.