[DRE-maint] Bug#1092987: vagrant: free Vagrant versions no longer work with HashiCorp Cloud Platform's Vagrant registry

[Lucas Nussbaum]

On 14/01/25 at 09:00 +0100, Lucas Nussbaum wrote:
> At this point, it's not clear if this change is intentional, so let's
> not discuss consequences at this point. I opened a ticket on HashiCorp's ZenDesk
> (https://support.hashicorp.com/hc/en-us/requests/171591)

TL;DR: HashiCorp support says "you need to update the Vagrant version if you want to use HCP Vagrant boxes"

Long version:
* I reported the issue and mentioned "I would like to continue using Vagrant 2.3.7 for legal reasons."
* HashiCorp support replied saying it works with 2.4.1, and "I would suggest you update to the latest Vagrant version and try again."
* I replied:
> I confirm that it works with Vagrant 2.4.0, but I am not able to move to Vagrant 2.4.0 for legal reasons (Business Software License).
> Does your message mean that HCP stops supporting Vagrant before 2.4.0 ?

* HashiCorp support replied:
> My message means that you need to update the Vagrant version if you want to use HCP Vagrant boxes.
> Vagrant is OSS tool: https://github.com/hashicorp/vagrant
> We do support only the HCP Vagrant (former Vagrant Cloud). We do support the only functionalities HCP Vagrant provides and the boxes from Hashicorp family: https://portal.cloud.hashicorp.com/vagrant/discover/hashicorp
> We do not support:
> * Vagrant OSS issues
> * Vagrant provider issues
> * Issues with specific user's box


I would like to propose the following plan, both as the one who
volunteered to continue to maintain the Vagrant package, and who
maintains the official Vagrant boxes.

# Regarding the Vagrant package in Debian

* Do not try to fix the package in unstable/testing, as this would be
  cumbersome without looking at the BSL-licensed code. (I personally do
  not want to take that legal risk)
* Remove the package from unstable (and testing, thus trixie).
* Do not change the package in stable and oldstable (it's broken, but
  still usable if someone downloads boxes manually, for example).

The advice for people depending on Vagrant should probably be to look at
alternatives (Incus comes to mind), or use the BSL-licensed Vagrant
package provided by HashiCorp.

# Regarding the HCP-hosted Vagrant images for Debian
# (https://portal.cloud.hashicorp.com/vagrant/discover/debian)

I do not plan to continue to maintain them (build/test/update them), as
they are no longer useful with the Free Vagrant versions.

I think that what serves our users best is to leave them available on
HCP, but to add a message stating that they are no longer updated.
(I don't think that removing the images from HCP is useful)


If you would like to step forward to maintain the package or the HCP
Vagrant images, please say so here.

Lucas