Bug 200614 - sysutils/vagrant: errors running after ruby updates
Summary: sysutils/vagrant: errors running after ruby updates
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Michael Moll
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-03 15:26 UTC by Nick Price
Modified: 2015-06-08 22:50 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (joe)

Attachments
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 Nick Price 2015-06-03 15:26:56 UTC 
After upgrading to the latest set of packages, I get the following output when I attempt to run vagrant:

*****

[nprice@freebsd ~/Homestead]$ vagrant
WARN: Unresolved specs during Gem::Specification.reset:
      net-ssh (< 2.10.0, >= 2.6.5, >= 2.6.6)
      builder (>= 2.1.2)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/usr/local/lib/ruby/gems/2.1/gems/vagrant-1.6.5/bin/vagrant:189:in `rescue in <top (required)>': cannot load such file -- vagrant/errors (LoadError)
        from /usr/local/lib/ruby/gems/2.1/gems/vagrant-1.6.5/bin/vagrant:106:in `<top (required)>'
        from /usr/local/bin/vagrant:23:in `load'
        from /usr/local/bin/vagrant:23:in `<main>'

*****

The following ruby packages were involved in the upgrade:

        rubygem-rb-fsevent: 0.9.4 -> 0.9.5
        rubygem-rack: 1.4.5,3 -> 1.4.5_1,3
        rubygem-main: 6.0.0 -> 6.1.0
        rubygem-httpclient: 2.4.0 -> 2.6.0.1
        rubygem-bundler: 1.7.14 -> 1.10.2
        ruby21-gems: 2.4.6 -> 2.4.7
Comment 1 Michael Moll freebsd_committer freebsd_triage 2015-06-06 00:20:50 UTC 
take.
Comment 2 Michael Moll freebsd_committer freebsd_triage 2015-06-06 00:35:49 UTC 
reverting the rubygem-bundler update seems to fix this.
Comment 3 Michael Moll freebsd_committer freebsd_triage 2015-06-06 00:51:49 UTC 
furthermore, it works with bundler 1.9.x, but not 1.10.x
Comment 4 Po-Chuan Hsieh freebsd_committer freebsd_triage 2015-06-08 19:45:34 UTC 
FYI, sysutils/rubygem-bundler17 was added to ports tree. It can be used for vagrant 1.7.3 which requires bundler < 1.8.0.
Comment 5 commit-hook freebsd_committer freebsd_triage 2015-06-08 22:49:08 UTC 
A commit references this bug:

Author: mmoll
Date: Mon Jun  8 22:48:53 UTC 2015
New revision: 388890
URL: https://svnweb.freebsd.org/changeset/ports/388890

Log:
  sysutils/vagrant: use sysutils/bundler17

  while here, sort and fix plist

  PR:		200614
  Differential Revision:	https://reviews.freebsd.org/D2760
  Approved by:	mat (mentor)

Changes:
  head/sysutils/vagrant/Makefile
  head/sysutils/vagrant/files/patch-vagrant.gemspec
  head/sysutils/vagrant/pkg-plist
Comment 6 Michael Moll freebsd_committer freebsd_triage 2015-06-08 22:50:52 UTC 
Thanks for rising this, it should be fixed now.
Please report back, if not.