Bug 207184 - sysutils/vagrant: vagrant "plugins" subcommand fails
Summary: sysutils/vagrant: vagrant "plugins" subcommand fails
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Mark Felder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-14 12:17 UTC by Armin Gruner
Modified: 2016-03-20 19:12 UTC (History)
2 users (show)

See Also:
joe: maintainer-feedback+


Attachments
[patch] sysutils/vagrant: fix group_by method missing in bundler gem. (994 bytes, patch)
2016-03-11 00:36 UTC, joe
joe: maintainer-approval+
Details | Diff
Poudriere Build Log (29.65 KB, text/x-log)
2016-03-11 00:37 UTC, joe
joe: maintainer-approval+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Gruner 2016-02-14 12:17:39 UTC
The vagrant "plugin install/uninstall/upgrade" subcommands fail with the Ruby traceback given below.

The "plugin" subcommand works if I use iocage for a pristine 10.2-RELEASE, rvm for an isolated ruby gem environment (ruby version 2.1.5), and checking out the 1.8.1 release from the vagrant GIT repository, building gem(s), and installing.

So I assume the dependency version may differ and will cause some incompatibility.


Unfortunately I've found no references how to do rubygem-ports development to  supply some patch.

Regards,
Armin



# vagrant --version
Vagrant 1.8.1
4b530a16-7b52-4106-80d4-cb69cd32b2f6# vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
/usr/local/lib/ruby/site_ruby/2.1/rubygems/specification.rb:945:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError)
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/bundler.rb:268:in `with_isolated_gem'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/bundler.rb:225:in `internal_install'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/bundler.rb:97:in `install'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/plugin/manager.rb:62:in `block in install_plugin'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/plugin/manager.rb:72:in `call'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/plugin/manager.rb:72:in `install_plugin'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/action/install_gem.rb:37:in `call'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/command/base.rb:14:in `action'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/command/install.rb:32:in `block in execute'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/command/install.rb:31:in `each'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/command/install.rb:31:in `execute'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/plugins/commands/plugin/command/root.rb:56:in `execute'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/cli.rb:42:in `execute'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/lib/vagrant/environment.rb:302:in `cli'
	from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.8.1/bin/vagrant:177:in `<top (required)>'
	from /usr/local/bin/vagrant:23:in `load'
	from /usr/local/bin/vagrant:23:in `<main>'
Comment 1 joe 2016-02-24 16:26:13 UTC
Hello,

The problem seems to be Vagrant itself. I've submitted a ticket with them.

https://github.com/mitchellh/vagrant/issues/7073

Thanks,
-Joe
Comment 2 joe 2016-03-01 22:32:59 UTC
Hello,

I have submitted a patch for this bug upstream. It is available on the above mentioned GitHub ticket.

Would you mind testing if the patch functions well under your environment?

Thank you for your time.
-Joe
Comment 3 Armin Gruner 2016-03-02 10:09:35 UTC
Yes, the patch fixes the vagrant installation via ports. Thanks!
Comment 4 joe 2016-03-11 00:36:37 UTC
Created attachment 167984 [details]
[patch] sysutils/vagrant: fix group_by method missing in bundler gem.
Comment 5 joe 2016-03-11 00:37:45 UTC
Created attachment 167985 [details]
Poudriere Build Log
Comment 6 joe 2016-03-11 00:38:18 UTC
Patch is ready for commit.

Best Regards,
-Joe
Comment 7 Mark Felder freebsd_committer freebsd_triage 2016-03-20 19:12:37 UTC
Committed, thanks!
Comment 8 commit-hook freebsd_committer freebsd_triage 2016-03-20 19:12:50 UTC
A commit references this bug:

Author: feld
Date: Sun Mar 20 19:11:53 UTC 2016
New revision: 411514
URL: https://svnweb.freebsd.org/changeset/ports/411514

Log:
  sysutils/vagrant: fix plugin subcommand

  PR:		207184

Changes:
  head/sysutils/vagrant/Makefile
  head/sysutils/vagrant/files/patch-lib_vagrant_bundler