Age | Commit message (Collapse) | Author | Files | Lines |
|
Co-authored-by: Nick Cao <nickcao@nichi.co>
|
|
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
|
|
2.2.19 doesn't work with VirtualBox version present in nixpkgs
* https://github.com/hashicorp/vagrant/blob/v2.3.4/CHANGELOG.md
|
|
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.
|
|
|
|
|
|
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.19/CHANGELOG.md#2219-november-5-2021
|
|
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.18/CHANGELOG.md#2218-july-27-2021
|
|
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.17/CHANGELOG.md#2217-july-7-2021
|
|
ChangeLog: https://github.com/hashicorp/vagrant/blob/v2.2.16/CHANGELOG.md#2216-april-29-2021
|
|
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`.
|
|
|
|
|
|
- remove trailing whitespace
- use spaces for indentation
|
|
https://github.com/hashicorp/vagrant/blob/v2.2.14/CHANGELOG.md#2214-november-20-2020
|
|
https://github.com/hashicorp/vagrant/blob/v2.2.13/CHANGELOG.md#2213-november-06-2020
|
|
https://github.com/hashicorp/vagrant/blob/main/CHANGELOG.md#2211-november-05-2020
|
|
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
|
|
https://github.com/hashicorp/vagrant/blob/v2.2.9/CHANGELOG.md#229-may-07-2020
|
|
https://github.com/hashicorp/vagrant/releases/tag/v2.2.8
|
|
|
|
|
|
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.
|
|
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.
|
|
https://github.com/hashicorp/vagrant/releases/tag/v2.2.7
|
|
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.
|
|
Just running `vagrant --version` was insufficient to catch #76629, but
this would have.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
|
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>
|
|
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
|
|
|
|
vagrant: 2.2.3 -> 2.2.5
|
|
|
|
|
|
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.
|
|
|
|
Fixes #55751
|
|
|
|
When using vagrant-libvirt as provider, the 'vagrant package'
command requires 'qemu-img' and 'virt-sysprep'.
|
|
libvirt and pkgconfig are now buildInputs to ruby-libvirt instead.
|
|
|
|
Patch taken from Debian
|
|
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":[]
}
}
}
|
|
|
|
Adds a flag and a new package to build vagrant with libvirt support,
to be able to install and use the vagrant-libvirt plugin.
|
|
|
|
|
|
|
|
This will cause Vagrant to use the rubygems version of bundler
without complaint.
|
|
The version was bumped but the dependencies were not updated.
Do so and add some instructions for future package updates.
|
|
|