Date: Sat, 13 Sep 2014 09:41:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193600] New: sysutils/vagrant broken by update to sysutils/rubygem-bundler Message-ID: <bug-193600-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193600 Bug ID: 193600 Summary: sysutils/vagrant broken by update to sysutils/rubygem-bundler Product: Ports Tree Version: Latest Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: Normal Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: christopherhall.hsw@gmail.com CC: joe@thrallingpenguin.com, ruby@FreeBSD.org CC: joe@thrallingpenguin.com, ruby@FreeBSD.org Running vagrant produces the error below % vagrant /usr/local/lib/ruby/site_ruby/2.0/rubygems/dependency.rb:247:in `to_specs': Could not find bundler (< 1.7.0, >= 1.5.2) amongst [akami-1.0.0, arrayfields-4.9.2, builder-3.0.4, bundler-1.7.2, celluloid-0.16.0, childprocess-0.5.3, chronic-0.10.2, diff-lcs-1.2.5, erubis-2.7.0, fattr-2.2.2, ffi-1.9.3, gssapi-1.0.2, gyoku-0.4.6, hitimes-1.2.2, hoe-3.12.0, httpclient-2.4.0, httpi-0.9.7, i18n-0.6.11, json_pure-1.8.1, listen-2.7.9, little-plugger-1.1.3, log4r-1.1.10, logging-1.8.2, main-6.0.0, map-6.5.4, multi_json-1.10.1, net-scp-1.1.2, net-ssh-2.7.0, nokogiri-1.6.3.1, nori-1.0.3, rack-1.4.5, rb-fsevent-0.9.4, rb-inotify-0.9.5, rb-kqueue-0.2.3, rspec-3.0.0, rspec-core-3.0.4, rspec-expectations-3.0.4, rspec-mocks-3.0.4, rspec-support-3.0.4, ruby-termios-0.9.6, rubyntlm-0.1.1, savon-0.9.5, timers-4.0.0, timers-1.1.0, uuidtools-2.1.5, vagrant-1.6.5, vagrant-1.6.3, wasabi-1.0.0, wdm-0.1.0, winrm-1.1.3] (Gem::LoadError) from /usr/local/lib/ruby/site_ruby/2.0/rubygems/specification.rb:778:in `block in activate_dependencies' from /usr/local/lib/ruby/site_ruby/2.0/rubygems/specification.rb:767:in `each' from /usr/local/lib/ruby/site_ruby/2.0/rubygems/specification.rb:767:in `activate_dependencies' from /usr/local/lib/ruby/site_ruby/2.0/rubygems/specification.rb:751:in `activate' from /usr/local/lib/ruby/site_ruby/2.0/rubygems.rb:1232:in `gem' from /usr/local/bin/vagrant:22:in `<main>' It seems that there ws a recent update of sysutils/rubygem-bundler by swills, SVN=366146 thane updated bundler to 1.7.2. However vagrant has a gemspec file that contains: s.add_dependency "bundler", ">= 1.5.2", "< 1.7.0" Manually changing the 1.7.0 to 1.8.0 in the port's work dir just after make extract, then doing "make reinstall" appears to work. Only limited testing done: up, provision, ssh and halt. I noted this on the vagrant github issues page as: https://github.com/mitchellh/vagrant/issues/4500 --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Maintainers CC'd -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193600-13>