Summary: | 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) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jay Faulkner <jayf> |
Component: | Current packages | Assignee: | Tim Harder <radhermit> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alunduil, ewoud+gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/schisamo/vagrant-omnibus/issues/36 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info vagrant
rubygems2 compatibility |
Description
Jay Faulkner
![]() Please attach the entire build log to this bug report. (In reply to Jeroen Roovers from comment #1) > Please attach the entire build log to this bug report. Oh, never mind that. 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. It appears newer versions of vagrant don't support >=rubygems-2.0 properly. This is something that should be reported upstream. Reported the issue upstream at https://github.com/mitchellh/vagrant/issues/2324. Created attachment 360892 [details, diff]
rubygems2 compatibility
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. Patched in the tree in 1.3.5. |