679446 – 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)

Bug 679446 - 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)

Summary: dev-ruby/net-telnet-0.1.1-r1 - /usr/lib64/ruby/2.4.0/rubygems.rb:17:in `requi...

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Ruby Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-03-04 20:44 UTC by MW
Modified:	2020-09-21 20:02 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge output (build-error.txt,4.50 KB, text/plain) 2019-03-04 20:44 UTC, MW	Details
output of emerge --info (emerge-info.txt,5.60 KB, text/plain) 2019-03-04 21:56 UTC, MW	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description MW 2019-03-04 20:44:59 UTC

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.

Comment 1 MW 2019-03-04 21:11:25 UTC

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

Comment 2 Jeroen Roovers (RETIRED) gentoo-dev

2019-03-04 21:44:38 UTC

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.

Comment 3 MW 2019-03-04 21:56:56 UTC

Created attachment 567818 [details]
output of emerge --info

See attachment for emerge --info.

eselect ruby list gives

Available Ruby profiles:
  [1]   ruby24 (with Rubygems) *

Comment 4 Jeroen Roovers (RETIRED) gentoo-dev

2019-03-05 05:30:25 UTC

(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?

Comment 5 Hans de Graaff gentoo-dev

2019-03-11 19:52:30 UTC

(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?

Comment 6 MW 2019-03-11 21:36:05 UTC

(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.

Comment 7 MW 2020-09-21 20:02:05 UTC

This bug is obsolete and not reproducible, since =dev-lang/ruby-2.4.5 no longer exists.