Conversation
hswong3i
added a commit
to alvistack/hashicorp-vagrant
that referenced
this pull request
Jan 10, 2026
git clean -xdf
git submodule sync --recursive
git submodule update --recursive --init
git submodule foreach --recursive git clean -xdf
gem build vagrant.gemspec -o ../vagrant-2.4.9.gem
bundle config set --local path ./bundle
bundle install --verbose --standalone
bundle config set --local cache_all true
bundle config set --local cache_all_platforms true
bundle cache
mv ../vagrant-2.4.9.gem ./vendor/cache/
rm -rf .bundle bundle vendor/bundle Gemfile.lock
tar zcvf ../vagrant_2.4.9.orig.tar.gz --exclude=.git .
debuild -uc -us
cp vagrant.spec ../vagrant_2.4.9-1.spec
cp vagrant.rpmlintrc /osc/home\:alvistack/hashicorp-vagrant-2.4.9/
cp ../vagrant*2.4.9*.{gz,xz,spec,dsc} /osc/home\:alvistack/hashicorp-vagrant-2.4.9/
rm -rf ../vagrant*2.4.9*.*
See https://build.opensuse.org/projects/Virtualization:vagrant/packages/vagrant/files/0001-bin-vagrant-silence-warning-about-installer.patch
See https://build.opensuse.org/projects/Virtualization:vagrant/packages/vagrant/files/0003-plugins-don-t-abuse-require_relative.patch.patch
See https://build.opensuse.org/projects/Virtualization:vagrant/packages/vagrant/files/0004-fix-vbox-package-boo-1044087-added-by-robert.muntean.patch
See https://build.opensuse.org/projects/Virtualization:vagrant/packages/vagrant/files/0006-do-not-abuse-relative-paths-in-docker-plugin-to-make.patch
See https://build.opensuse.org/projects/Virtualization:vagrant/packages/vagrant/files/0007-Don-t-abuse-relative-paths-in-plugins.patch
See https://src.fedoraproject.org/rpms/vagrant/blob/rawhide/f/vagrant-2.2.9-do-not-load-dependencies.patch
See https://src.fedoraproject.org/rpms/vagrant/blob/rawhide/f/vagrant-2.3.4-Fix-the-default-vagrant-URL-for-pulling-boxes.patch
See ffi/ffi#1036 (comment)
See ffi/ffi#1105 (comment)
See hashicorp#13773
Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pull request proposes removing the < 4 upper bound on required_ruby_version in the gemspec.
With Ruby 4.0 scheduled for release on Christmas Day and a preview already available.
Ruby 4.0.0 preview3 Released
https://www.ruby-lang.org/en/news/2025/12/18/ruby-4-0-0-preview3-released/
the current constraint prevents gem install hoe from working on Ruby 4.0. Dropping the upper bound ensures the gem will install cleanly on Ruby 4.0 and future Ruby versions.