| Summary: | dev-ruby/net-telnet-0.1.1-r1 - /usr/lib64/ruby/2.4.0/rubygems.rb:17:in `require': cannot load such file -- rubygems/compatibility (LoadError) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | MW <spamfilter-1> |
| Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge output
output of emerge --info |
||
Apparently this issue is not isolated to dev-ruby/net-telnet. Further investigation shows that the situation is the same for the following packages: dev-ruby/minitest-5.10.3 dev-ruby/rake-12.3.1 dev-ruby/did_you_mean-1.1.2 dev-ruby/power_assert-1.1.1 dev-ruby/xmlrpc-0.3.0 dev-ruby/json-2.1.0 dev-ruby/test-unit-3.2.7 Please post your `emerge --info` output in a comment. The output of `eselect ruby list` would also help as that is probably central to your problem. Created attachment 567818 [details]
output of emerge --info
See attachment for emerge --info.
eselect ruby list gives
Available Ruby profiles:
[1] ruby24 (with Rubygems) *
(In reply to MW from comment #1) > Apparently this issue is not isolated to dev-ruby/net-telnet. But that suggests to me that the problems for different packages have a common source. All dev-lang/ruby ebuilds RDEPEND on virtual/rubygems already. What would cause the rebuild of dev-ruby-rubygems to make a difference here? (In reply to Jeroen Roovers from comment #4) > (In reply to MW from comment #1) > > Apparently this issue is not isolated to dev-ruby/net-telnet. > > But that suggests to me that the problems for different packages have a > common source. All dev-lang/ruby ebuilds RDEPEND on virtual/rubygems > already. What would cause the rebuild of dev-ruby-rubygems to make a > difference here? This could happen RUBY_TARGETS would be passed as part of the emerge invocation. Was this a new install or an update from RUBY_TARGETS=ruby23? (In reply to Hans de Graaff from comment #5) > This could happen RUBY_TARGETS would be passed as part of the emerge > invocation. Was this a new install or an update from RUBY_TARGETS=ruby23? It was not a new install. According to the portage logs I had just gone from =dev-lang/ruby-2.3.8-r1 to =dev-lang/ruby-2.4.5, so I guess that would have changed the RUBY_TARGETS. This bug is obsolete and not reproducible, since =dev-lang/ruby-2.4.5 no longer exists. |
Created attachment 567814 [details] emerge output Emerging =dev-ruby/net-telnet-0.1.1-r1 fails with the attached build error. Emerging rubygems resolves the issue.