Bug 486096 – app-emulation/vagrant - vagrant plugin install [...]: /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubygems/format (LoadError)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jay Faulkner 2013-09-26 17:58:08 UTC]

Created attachment 359546 [details]
emerge --info vagrant

I can't install vagrant plugins on my system at all.

$ vagrant plugin install vagrant-omnibus
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubygems/format (LoadError)
	from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:51:in `require'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/action/install_gem.rb:3:in `<top (required)>'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/action.rb:12:in `block in action_install'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/action.rb:10:in `tap'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/action.rb:10:in `action_install'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/command/install.rb:27:in `execute'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/plugins/commands/plugin/command/root.rb:52:in `execute'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/lib/vagrant/cli.rb:38:in `execute'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/lib/vagrant/environment.rb:478:in `cli'
	from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.3.3/bin/vagrant:96:in `<top (required)>'
	from /usr/bin/vagrant:8:in `load'
	from /usr/bin/vagrant:8:in `<main>'


This bug appears to have been reported upstream, but was closed as related to package: https://github.com/schisamo/vagrant-omnibus/issues/36 -- however these failures occur when trying to install /any/ vagrant plugin.

emerge --info output attached.

[Comment 1 Jeroen Roovers (RETIRED) 2013-09-27 15:51:23 UTC]

Please attach the entire build log to this bug report.

[Comment 2 Jeroen Roovers (RETIRED) 2013-09-27 15:52:08 UTC]

(In reply to Jeroen Roovers from comment #1)
> Please attach the entire build log to this bug report.

Oh, never mind that.

[Comment 3 Alex Brandt (RETIRED) 2013-09-28 23:40:19 UTC]

Guess we can get this confirmed?  Also, I'm seeing this behavior in all versions in the tree >1.2.6.  What other details would be useful in solving this issue?  I'm not too strong in debugging ruby packaging like this but am willing to help if given a little guidance.

[Comment 4 Tim Harder 2013-09-29 05:41:53 UTC]

It appears newer versions of vagrant don't support >=rubygems-2.0 properly. This is something that should be reported upstream.

[Comment 5 Alex Brandt (RETIRED) 2013-10-04 16:23:08 UTC]

Reported the issue upstream at https://github.com/mitchellh/vagrant/issues/2324.

[Comment 6 Tiago Macedo 2013-10-14 16:39:48 UTC]

Created attachment 360892 [details, diff]
rubygems2 compatibility

[Comment 7 Tiago Macedo 2013-10-14 16:41:06 UTC]

Unfortunately upstream bundles rubygems (currently 1.8) in their packages so they don't care about this issue, which is now closed.

I have a patch for it that makes it - as far as I noticed - compatible with both versions of rubygems. I'll try to get it upstream but in the meanwhile I put it in my overlay ( https://github.com/tmacedo/portage ) and here as an attachment.

[Comment 8 Tim Harder 2013-10-18 05:45:13 UTC]

Patched in the tree in 1.3.5.