Summary: | dev-ruby/rake-0.9.6-r1 - src-install(): /usr/bin/ruby18 -- auto_gem (LoadError) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] Development | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2014-01-07 07:49:24 UTC
root@caiman:/usr/local/portage/media-gfx(45)# eselect ruby list Available Ruby profiles: [1] ruby18 [2] ruby19 (with Rubygems) * [3] ruby20 (with Rubygems) (In reply to Juergen Rose from comment #1) > root@caiman:/usr/local/portage/media-gfx(45)# eselect ruby list > Available Ruby profiles: > [1] ruby18 > [2] ruby19 (with Rubygems) * > [3] ruby20 (with Rubygems) At all other systems 'eselect ruby list' says: root@impala:/root(26)# eselect ruby list Available Ruby profiles: [1] ruby18 (with Rubygems) * [2] ruby19 (with Rubygems) [3] ruby20 (with Rubygems) [4] ruby21 (with Rubygems) root@lynx2:/usr/local/portage/net-fs(68)# eselect ruby list Available Ruby profiles: [1] ruby18 (with Rubygems) [2] ruby19 (with Rubygems) * [3] ruby20 (with Rubygems) [4] ruby21 (with Rubygems) So anyway Rubygems is missing for ruby18 on caiman. Even after reemerging =ruby-1.8.7_p374-r1 I still have: root@caiman:/usr/src(60)# eselect ruby list Available Ruby profiles: [1] ruby18 [2] ruby19 (with Rubygems) * [3] ruby20 (with Rubygems) And 'USE=-doc emerge -v1 rake' still fails with the same error. After reemerging rubygems root@caiman:/usr/src(64)# emerge -v1 rubygems These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-ruby/rubygems-2.0.14 USE="server {-test}" RUBY_TARGETS="ruby18* ruby19 ruby20 ruby21 -jruby" 0 kB 'eselect ruby list' shows again ruby18 (with Rubygems) and also 'USE=-doc emerge -v1 rake' works. I think this is another manifestion of the problem where rubygems would be recompiled without ruby18 support during an update while ruby18 was still eselected. I'm closing this bug given that we can't fix this situation now. For ruby19 -> ruby20 we'll encourage people more strongly and at an earlier stage to select ruby20 before we mask ruby19. |