vagrant-2.3.0 has been released, please update ebuild. Reproducible: Always
Since app-emulation/virtualbox having version 7 in portage, vagrant version <2.3.2 doesn't work with provider virtualbox anymore with Virtualbox 7 installed. Either bump the version to 2.3.2 or set a dependency to <app-emulation/virtualbox-7.
Hey, I will work on the ebuild for a 2.3.x release. Tino: About the issue with virtualbox-7 and vagrant-2.3.2, there an issue on the github: https://github.com/hashicorp/vagrant/issues/12968
bump, a few months have gone by since the creation of this bug report, to help speed up this process I would be willing to work on an updated ebuild for vagrant-2.3.4 and maintain for later releases, just need some guidance on the process of submitting new ebuilds to gentoo's repo for vagrant-2.3.4 new build dependencies.
(In reply to claws from comment #3) > bump, a few months have gone by since the creation of this bug report, to > help speed up this process I would be willing to work on an updated ebuild > for vagrant-2.3.4 and maintain for later releases, just need some guidance > on the process of submitting new ebuilds to gentoo's repo for vagrant-2.3.4 > new build dependencies. You can create a pull requests on github. There's a lot of documentation here: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Thank you!
Created attachment 845942 [details] vagrant-2.3.4.ebuild I ran out of steam on this, but I made a start. These should help. There's another new dependency, grpc. I'm not sure whether that should be part of net-libs/grpc. Probably not.
Created attachment 845944 [details] googleapis-common-protos-types-1.4.0.ebuild
missing dependency $ vagrant up Traceback (most recent call last): 6: from /usr/lib64/ruby/gems/2.7.0/gems/vagrant-2.3.4/bin/vagrant:105:in `<main>' 5: from /usr/lib64/ruby/gems/2.7.0/gems/vagrant-2.3.4/bin/vagrant:94:in `block in <main>' 4: from /usr/lib64/ruby/gems/2.7.0/gems/vagrant-2.3.4/bin/vagrant:94:in `each' 3: from /usr/lib64/ruby/gems/2.7.0/gems/vagrant-2.3.4/bin/vagrant:95:in `block (2 levels) in <main>' 2: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:62:in `gem' 1: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/dependency.rb:323:in `to_spec' /usr/lib64/ruby/site_ruby/2.7.0/rubygems/dependency.rb:311:in `to_specs': Could not find 'grpc' (>= 0) among 89 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/xxxxxxx/.gem/ruby/2.7.0:/usr/lib64/ruby/gems/2.7.0:/usr/local/lib64/ruby/gems/2.7.0', execute `gem env` for more information
Like I said, it's not finished.
Hi, sorry for the delay, I made ebuilds for all of vagrant's 2.3.x dependencies, currently stuck troubleshooting some protobuf bug, any help is appreciated
Created attachment 848318 [details] googleapis-common-protos-types-1.4.0.ebuild
Created attachment 848320 [details] google-protobuf-3.21.12.ebuild
Created attachment 848322 [details] grpc-1.49.2.ebuild
Created attachment 848324 [details] ipaddr-1.2.5.ebuild
Created attachment 848326 [details] rgl-0.5.10.ebuild
Created attachment 848328 [details] vagrant-2.3.4.ebuild
(In reply to claws from comment #9) > Hi, sorry for the delay, I made ebuilds for all of vagrant's 2.3.x > dependencies, currently stuck troubleshooting some protobuf bug, any help is > appreciated Hi, is that: <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- google/protobuf/descriptor_pb (LoadError) from <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/lib64/ruby/gems/3.0.0/gems/google-protobuf-3.21.12/lib/google/protobuf/descriptor_dsl.rb:9:in `<top (required)>' from <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require' from <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require' Just to be sure it's the same, because I've modified your ebuilds to work with ruby-3.0
(In reply to Mike Limansky from comment #16) > (In reply to claws from comment #9) > > Hi, sorry for the delay, I made ebuilds for all of vagrant's 2.3.x > > dependencies, currently stuck troubleshooting some protobuf bug, any help is > > appreciated > > Hi, is that: > > <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require. > rb>:85:in `require': cannot load such file -- google/protobuf/descriptor_pb > (LoadError) > from > <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require. > rb>:85:in `require' > from > /usr/lib64/ruby/gems/3.0.0/gems/google-protobuf-3.21.12/lib/google/protobuf/ > descriptor_dsl.rb:9:in `<top (required)>' > from > <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require. > rb>:85:in `require' > from > <internal:/usr/lib64/ruby/site_ruby/3.0.0/rubygems/core_ext/kernel_require. > rb>:85:in `require' > > Just to be sure it's the same, because I've modified your ebuilds to work > with ruby-3.0 Hi, yes it's the same error, sorry but haven't made any progress since and will be very busy until the end of the month.
Sorry for the delay but life got in the way, I'm back working on this now, I've fixed the ebuild for google-protobuf but dev-ruby/grpc has been a major pain to deal with, I've managed to get it to build with dev-cpp/abseil-cpp-20220623.1 but when trying to load vagrant it gives a "symbol undefined" error for grpc_c.so, with different versions of dev-cpp/abseil-cpp it won't even build ... honestly have no clue how to fix this, hope someone has more experience with this and can help.
Created attachment 861918 [details] google-protobuf-3.23.0.ebuild
Created attachment 861919 [details] googleapis-common-protos-types-1.6.0.ebuild
Created attachment 861920 [details] grpc-1.54.1.ebuild
Created attachment 861921 [details] vagrant-2.3.4.ebuild bumped ruby to ruby31
Created attachment 861922 [details] ipaddr-1.2.5.ebuild bumped ruby to ruby31
Created attachment 861923 [details] rgl-0.5.10.ebuild bumped ruby to ruby31
Could you make a GitHub PR instead? It's a bit hard to justify all the separate attachments.
(In reply to Sam James from comment #25) > Could you make a GitHub PR instead? It's a bit hard to justify all the > separate attachments. Sure, do I make a separate PR for each package ? or just one for vagrant-2.3.4 ?
(In reply to claws from comment #26) > (In reply to Sam James from comment #25) > > Could you make a GitHub PR instead? It's a bit hard to justify all the > > separate attachments. > > Sure, do I make a separate PR for each package ? or just one for > vagrant-2.3.4 ? Thanks! One PR, but with multiple commits (one per package).
Mark, you still with us? I need you to add signoff to the stuff in https://github.com/gentoo/gentoo/pull/31609.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e419db21acd6e588b8d12b7f59e48aff873917fb commit e419db21acd6e588b8d12b7f59e48aff873917fb Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2023-08-27 16:57:48 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2023-08-27 16:58:57 +0000 app-emulation/vagrant: add 2.3.7 Closes: https://bugs.gentoo.org/867943 Closes: https://bugs.gentoo.org/912592 Signed-off-by: Hans de Graaff <graaff@gentoo.org> app-emulation/vagrant/Manifest | 1 + app-emulation/vagrant/files/vagrant.in | 2 +- app-emulation/vagrant/vagrant-2.3.7.ebuild | 121 +++++++++++++++++++++++++++++ 3 files changed, 123 insertions(+), 1 deletion(-)
