about summary refs log tree commit diff
path: root/pkgs/development/tools/vagrant
AgeCommit message (Collapse)AuthorFilesLines
2023-05-12vagrant: allow un-disabling of version checkAndrew1-1/+1
Co-authored-by: Nick Cao <nickcao@nichi.co>
2023-05-11vagrant: disable version checkAndrew Kvalheim1-1/+2
Silences messages such as: > A new version of Vagrant is available: 2.3.4 (installed version: 2.2.19)! Documentation: https://developer.hashicorp.com/vagrant/docs/v2.2.19/other/environmental-variables#vagrant_checkpoint_disable
2023-04-07vagrant: 2.2.19 -> 2.3.4Roman Melnikov3-45/+309
2.2.19 doesn't work with VirtualBox version present in nixpkgs * https://github.com/hashicorp/vagrant/blob/v2.3.4/CHANGELOG.md
2023-03-03treewide: remove ma27 from a bunch of packages (again)Maximilian Bosch1-1/+1
Some of the stuff used to be needed for a project, for others I found alternatives that suited better my needs. Anyways, I don't intend to spend time maintaining these, so no need to keep that.
2022-05-11vagrant: libvirt-provider: 0.7.0 -> 0.8.2Maximilian Bosch1-6/+6
2022-03-16vagrant-libvirt: 0.4.0 -> 0.7.0teutat3s1-27/+37
2021-11-06vagrant: 2.2.18 -> 2.2.19Maximilian Bosch2-14/+14
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.19/CHANGELOG.md#2219-november-5-2021
2021-07-28vagrant: 2.2.17 -> 2.2.18Maximilian Bosch2-9/+9
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.18/CHANGELOG.md#2218-july-27-2021
2021-07-08vagrant: 2.2.16 -> 2.2.17Maximilian Bosch2-18/+28
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.17/CHANGELOG.md#2217-july-7-2021
2021-04-30vagrant: 2.2.15 -> 2.2.16Maximilian Bosch2-6/+6
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.16/CHANGELOG.md#2216-april-29-2021
2021-03-31vagrant: 2.2.14 -> 2.2.15Maximilian Bosch4-51/+394
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.15/CHANGELOG.md#2215-march-30-2021 Also had to revert a change which improved plugin-errors a bit since it changed the dependency resolution in a way that broke `vagrant-libvirt` from `$out/vagrant-plugins/plugins.d`.
2021-03-03vagrant: remove unused inputSandro Jäckel1-1/+1
2021-01-22treewide: add final newlinezowoq2-2/+2
2021-01-21treewide: editorconfig fixeszowoq1-1/+1
- remove trailing whitespace - use spaces for indentation
2020-11-23vagrant: 2.2.13 -> 2.2.14Maximilian Bosch2-8/+8
https://github.com/hashicorp/vagrant/blob/v2.2.14/CHANGELOG.md#2214-november-20-2020
2020-11-11vagrant: 2.2.11 -> 2.2.13Maximilian Bosch2-4/+4
https://github.com/hashicorp/vagrant/blob/v2.2.13/CHANGELOG.md#2213-november-06-2020
2020-11-06vagrant: 2.2.10 -> 2.2.11Maximilian Bosch3-108/+75
https://github.com/hashicorp/vagrant/blob/main/CHANGELOG.md#2211-november-05-2020
2020-08-25vagrant: 2.2.9 -> 2.2.10Maximilian Bosch4-38/+37
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.10/CHANGELOG.md#2210-august-24-2020 Apart from the usual `gemset`-update the following patches were altered: * Deprecation fix on ruby 2.6.5: was removed since the underlying issue was fixed upstream. * 0004-Support-system-installed-plugins.patch: re-downloaded the rebased version from `salsa.debian.org`[1] where we originally obtained the patch from. * use-system-bundler-version: re-applied on top of Vagrant 2.2.10. [1] https://salsa.debian.org/ruby-team/vagrant/-/blob/9d86f222/debian/patches/0004-Support-system-installed-plugins.patch
2020-06-17vagrant: 2.2.8 -> 2.2.9Maximilian Bosch2-8/+8
https://github.com/hashicorp/vagrant/blob/v2.2.9/CHANGELOG.md#229-may-07-2020
2020-05-05vagrant: 2.2.7 -> 2.2.8Maximilian Bosch2-21/+20
https://github.com/hashicorp/vagrant/releases/tag/v2.2.8
2020-04-10treewide: Per RFC45, remove all unquoted URLsMichael Reilly1-1/+1
2020-03-24vagrant: remove aneeshusa as maintainerAneesh Agrawal1-1/+1
2020-02-05Revert "Revert "Merge master into staging-next""Frederik Rietdijk2-20/+28
In 87a19e9048773d5a363679617406ad148d36c3b8 I merged staging-next into master using the GitHub gui as intended. In ac241fb7a570d6cf81d229ad22a8889602639160 I merged master into staging-next for the next staging cycle, however, I accidentally pushed it to master. Thinking this may cause trouble, I reverted it in 0be87c79797a5fa384fbc356c74ed54f9f7829ea. This was however wrong, as it "removed" master. This reverts commit 0be87c79797a5fa384fbc356c74ed54f9f7829ea.
2020-02-05Revert "Merge master into staging-next"Frederik Rietdijk2-28/+20
I merged master into staging-next but accidentally pushed it to master. This should get us back to 87a19e9048773d5a363679617406ad148d36c3b8. This reverts commit ac241fb7a570d6cf81d229ad22a8889602639160, reversing changes made to 76a439239eb310d9ad76d998b34d5d3bc0e37acb.
2020-02-05vagrant: 2.2.6 -> 2.2.7Maximilian Bosch2-20/+28
https://github.com/hashicorp/vagrant/releases/tag/v2.2.7
2020-01-14vagrant: Unbreak replacing symlinks on macOSMike Sperber1-0/+2
On a local installation on macOS, "cp -a" creates a write-protected directory, which can't be renamed. Do a "chmod +w" to unbreak. Fixes #77671.
2019-12-31vagrant: Improve installCheckPhase to verify an actual operationAnders Kaseorg1-6/+1
Just running `vagrant --version` was insufficient to catch #76629, but this would have. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2019-12-31vagrant: Resolve crash by replacing gem symlinks with directoriesAnders Kaseorg1-0/+11
This workaround was discovered by painstakingly resolving the differences between a working installation and a non-working installation until a minimal change was found. I have no idea why it works. Fixes #76629. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2019-11-06vagrant: 2.2.5 -> 2.2.6Maximilian Bosch2-92/+93
https://github.com/hashicorp/vagrant/releases/tag/v2.2.6 Generated the `gemset.nix` by converting the `vagrant.gemspec` file to a different `Gemfile` as described in the previous update PR[1]. [1] https://github.com/NixOS/nixpkgs/pull/64302#issuecomment-516837953
2019-09-08treewide: remove redundant quotesvolth1-1/+1
2019-08-02Merge pull request #64302 from angristan/vagrant/update/2.2.5Maximilian Bosch2-99/+38
vagrant: 2.2.3 -> 2.2.5
2019-07-31vagrant: 2.2.3 -> 2.2.5angristan2-99/+38
2019-07-27vagrant: add bash completionsMeghea Iulian1-0/+3
2019-06-19vagrant: Don't patch salt provisioner's shebangSamuel Dionne-Riel1-0/+7
The script is intended to run on remote systems, not on the local system. The shebang **has** to work where nix and the current store does not exist.
2019-03-05vagrant: re-add nowarn patch (#56863)William Kral1-0/+1
2019-02-25vagrant: only use libvirt on linuxMatthew Bauer1-1/+2
Fixes #55751
2019-02-12vagrant: 2.2.0 -> 2.2.3Florian Klink3-32/+56
2019-01-02vagrant: Add vagrant-libvirt utility dependenciesRyan Fitzsimon1-3/+15
When using vagrant-libvirt as provider, the 'vagrant package' command requires 'qemu-img' and 'virt-sysprep'.
2018-12-17vagrant: Remove unnecessary buildInputsMatthew Harm Bekkema1-9/+2
libvirt and pkgconfig are now buildInputs to ruby-libvirt instead.
2018-12-17vagrant: Install vagrant-libvirt as system pluginMatthew Harm Bekkema2-0/+14
2018-12-17vagrant: Support system-installed pluginsMatthew Harm Bekkema2-0/+106
Patch taken from Debian
2018-12-17vagrant: Add vagrant-libvirt to the gemsetMatthew Harm Bekkema1-6/+105
With this, you can "install" the plugin just by adding the following to ~/vagrant.d/plugins.json: { "version":"1", "installed": { "vagrant-libvirt": { "ruby_version":"2.5.3", "vagrant_version":"2.2.0", "gem_version":"", "require":"", "sources":[] } } }
2018-11-07vagrant: do withLibvitr by default #49220Christian Albrecht1-1/+1
2018-11-07vagrant-libvirt: init at 2.2.0Christian Albrecht2-4/+30
Adds a flag and a new package to build vagrant with libvirt support, to be able to install and use the vagrant-libvirt plugin.
2018-11-07vagrant: 2.1.2 -> 2.2.0Christian Albrecht2-21/+30
2018-10-01vagrant: remove unused vendored Gemfile{,.lock}Aneesh Agrawal3-156/+4
2018-09-25vagrant: Clean up GemfileAneesh Agrawal1-1/+1
2018-08-27vagrant: mark bundler as system pluginAneesh Agrawal2-0/+14
This will cause Vagrant to use the rubygems version of bundler without complaint.
2018-07-16vagrant: update deps for 2.1.2Aneesh Agrawal3-53/+7
The version was bumped but the dependencies were not updated. Do so and add some instructions for future package updates.
2018-07-14vagrant: 2.1.1 -> 2.1.2 (#43416)Alyssa Ross1-2/+2