Package Details: vagrant 2.4.9-1

Git Clone URL: https://aur.archlinux.org/vagrant.git (read-only, click to copy)
Package Base: vagrant
Description: Build and distribute virtualized development environments
Upstream URL: https://vagrantup.com
Licenses: BUSL-1.1
Conflicts: vagrant-substrate
Replaces: vagrant-substrate
Submitter: gromit
Maintainer: mackilanu
Last Packager: mackilanu
Votes: 19
Popularity: 3.68
First Submitted: 2025-04-18 09:42 (UTC)
Last Updated: 2025-08-21 21:06 (UTC)

Latest Comments

1 2 Next › Last »

TheRainbowSheep commented on 2025-08-26 07:30 (UTC) (edited on 2025-08-26 07:30 (UTC) by TheRainbowSheep)

I manage several ruby versions using rvm, and I had the same issue as @leaveye. The solution was to run rvm use system before building the package with makepkg.

And of course it assumes you use system ruby (rvm use system) when you use vagrant.

mackilanu commented on 2025-08-19 15:06 (UTC)

@pludikovsky Thanks for the patch. I have now updated the PKGBUILD.

pludikovsky commented on 2025-08-18 09:15 (UTC)

Please add cdrtools to the optdepends, as it's needed for cloud-init media creation.

Patch:

diff --git a/PKGBUILD b/PKGBUILD
index 5b89400..2861b48 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -19,7 +19,8 @@ options=('!emptydirs')
 depends=('curl' 'libarchive' 'libssh2' 'libxml2' 'libxslt' 'rsync'
   'ruby' 'xz' 'perl')
 makedepends=('git' 'go')
-optdepends=('dnsmasq: if using libvirt')
+optdepends=('dnsmasq: if using libvirt'
+   'cdrtools: to create cloud-init media')
 conflicts=('vagrant-substrate')
 replaces=('vagrant-substrate')
 source=("$pkgname-$pkgver.tar.gz::https://github.com/hashicorp/$pkgname/archive/v$pkgver.tar.gz"

punkoivan commented on 2025-05-11 17:03 (UTC)

Thanks for the package. Also faced that bug after updating system. Reinstalled package, just didn't want to mess with ruby packages. Now works well.

leaveye commented on 2025-05-08 08:39 (UTC)

@Kppqju77 thanks alot. after completely remove ~/.cache/paru/clone/vagrant then reinstall works for me.

mackilanu commented on 2025-05-07 11:03 (UTC)

@leaveye @Kppqju77 Interesting, i have not been able to replicate that issue on my machine. Did reinstalling fix it for both of you?

Kppqju77 commented on 2025-05-07 10:34 (UTC)

@leaveye: Had the same issue, clean building and re-installing it made it work

leaveye commented on 2025-05-06 06:00 (UTC)

need additional dependency or something like that?

❯ LANG=C paru -Qi vagrant
Name            : vagrant
Version         : 2.4.5-1
Description     : Build and distribute virtualized development environments
Architecture    : x86_64
URL             : https://vagrantup.com
Licenses        : BUSL-1.1
Groups          : None
Provides        : None
Depends On      : curl  libarchive  libssh2  libxml2  libxslt  rsync  ruby  xz  perl
Optional Deps   : dnsmasq: if using libvirt [installed]
Required By     : None
Optional For    : pycharm-eap
Conflicts With  : vagrant-substrate
Replaces        : vagrant-substrate
Installed Size  : 22.58 MiB
Packager        : Unknown Packager
Build Date      : Fri Apr 25 18:36:56 2025
Install Date    : Fri Apr 25 18:38:02 2025
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : None

❯ vup && vssh && vh
/usr/lib/ruby/3.4.0/rubygems/dependency.rb:303:in 'Gem::Dependency#to_specs': Could not find 'bcrypt_pbkdf' (>= 1.1) - did find: [bcrypt_pbkdf-1.1.1] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/opt/vagrant/embedded/gems:/usr/lib/ruby/gems/3.3.0:/opt/vagrant/embedded/gems:/usr/lib/ruby/gems/3.3.0' , execute `gem env` for more information
        from /usr/lib/ruby/3.4.0/rubygems/dependency.rb:313:in 'Gem::Dependency#to_spec'
        from /usr/lib/ruby/3.4.0/rubygems/core_ext/kernel_gem.rb:56:in 'Kernel#gem'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.5/bin/vagrant:95:in 'block (2 levels) in <main>'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.5/bin/vagrant:94:in 'Array#each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.5/bin/vagrant:94:in 'block in <main>'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.5/bin/vagrant:105:in '<main>'
❯ 

gromit commented on 2025-05-03 11:02 (UTC)

@mackilanu, please have a look at https://wiki.archlinux.org/title/AUR_submission_guidelines#Publishing_new_package_content :)

mackilanu commented on 2025-05-03 11:00 (UTC) (edited on 2025-05-03 11:01 (UTC) by mackilanu)

@JisuWoniu I was not aware of makepkg --printsrcinfo. Very convenient, thanks!

.SRCINFO has been updated now.