Created attachment 211602 [details] output of pkg info After fresh pkg install vagrant on 11.3-STABLE amd64 (r356413) I am trying to bootstrap git://github.com/rails/rails-dev-box.git (at 4d87263a16cb70a8883dbe3446be60dcdc870116) with vagrant: > vagrant up Traceback (most recent call last): 8: from /usr/local/bin/vagrant:23:in `<main>' 7: from /usr/local/lib/ruby/site_ruby/2.6/rubygems.rb:304:in `activate_bin_path' 6: from /usr/local/lib/ruby/site_ruby/2.6/rubygems.rb:304:in `synchronize' 5: from /usr/local/lib/ruby/site_ruby/2.6/rubygems.rb:305:in `block in activate_bin_path' 4: from /usr/local/lib/ruby/site_ruby/2.6/rubygems/specification.rb:1417:in `activate' 3: from /usr/local/lib/ruby/site_ruby/2.6/rubygems/specification.rb:1435:in `activate_d oependencies' 2: from /usr/local/lib/ruby/site_ruby/2.6/rubygems/specification.rb:1435:in `each' 1: from /usr/local/lib/ruby/site_ruby/2.6/rubygems/specification.rb:1446:in `block in activate_dependencies' /usr/local/lib/ruby/site_ruby/2.6/rubygems/dependency.rb:313:in `to_specs': Could not find 'rubyzip' (~> 1.3) - did find: [rubyzip-2.2.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/saper/.gem/ruby/2.6:/usr/local/lib/ruby/gems/2.6', execute `gem env` for more information I have rubygem-rubyzip-2.2.0 installed, but not rubygem-rubyzip13 pkg info output attached
Having installed rubygem-rubyzip13, it gets worse: /usr/local/lib/ruby/site_ruby/2.6/rubygems/specification.rb:2298:in `raise_if_conflicts': Unable to activate winrm-fs-1.3.4, because rubyzip-1.3.0 conflicts with rubyzip (~> 2.0) (Gem::ConflictError)
The latter seems to be https://github.com/hashicorp/vagrant/issues/11375, got it running by replacing all references to rubyzip 1.3 to 2.0 in the following files: /usr/local/lib/ruby/gems/2.6/gems/vagrant-2.2.7/vagrant.gemspec /usr/local/lib/ruby/gems/2.6/specifications/vagrant-2.2.7.gemspec
from attachment 211602 [details]: > vagrant-2.2.7 Vagrant Virtual Machine Manager cmt@ has committed a fix (r525611) to update rubyzip requirement. It is vagrant-2.2.7_1 now. Please update ports tree and try again.
fix committed 3 months ago, never heard back, "works for me"