Date: Thu, 18 Apr 2024 13:02:17 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278431] sysutils/vagrant rubygem dependency version issue Message-ID: <bug-278431-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278431 Bug ID: 278431 Summary: sysutils/vagrant rubygem dependency version issue Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: sidicer@gmail.com CC: joe@thrallingpenguin.com CC: joe@thrallingpenguin.com Flags: maintainer-feedback?(joe@thrallingpenguin.com) Vagrant reports dependency issue on fresh install: ``` /usr/local/lib/ruby/site_ruby/3.2/rubygems/dependency.rb:315:in `to_specs': Could not find 'childprocess' (~> 4.1.0) - did find: [childprocess-5.0.0] (Gem::MissingSpecVersionError) ``` --- When installing `vagrant` package rubygem dependencies are installed with t= heir latest versions, but [vagrant.gemspec](https://raw.githubusercontent.com/hashicorp/vagrant/main/= vagrant.gemspec) expects `rubygem-childprocess` package to be version `4.1.0` (installed: `5.0.0`) and `rubygem-vagrant_cloud` to be version `3.0.5` (installed: `3.1= .1`) ``` # vagrant.gemspec: s.add_dependency "vagrant_cloud", "~> 3.1.1" s.add_dependency "childprocess", "~> 4.1.0" ``` "Dirty" fix is to modify `/usr/local/lib/ruby/gems/3.2/specifications/vagrant-2.3.7.gemspec` and set= the version of actually installed packages. ``` s.add_runtime_dependency(%q<childprocess>.freeze, ["~> 5.0.0".freeze]) s.add_runtime_dependency(%q<vagrant_cloud>.freeze, ["~> 3.1.1".freeze]) ``` Not sure at the moment if it is a port dependency issue or if this should be directed to `hashicorp/vagrant` --=20 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-278431-7788>