Hi Sachse, On 03/02/25 at 14:58 +0100, Sachse wrote: > Package: cloud.debian.org > Severity: normal > > Dear Maintainer, > > while trying to update the 'debian/bookworm64' Vagrant Box, I get an error > stating: > "The metadata for the box was malformed." > > > The longer command output looks like this: > ``` > ❯ vagrant box list > debian/bookworm64 (virtualbox, 12.20241217.1, (amd64)) > > ❯ vagrant box update --box debian/bookworm64 > Checking for updates to 'debian/bookworm64' > Latest installed version: 12.20241217.1 > Version constraints: > 12.20241217.1 > Provider: virtualbox > Architecture: "amd64" > The metadata for the box was malformed. The exact error > is shown below. Please contact the maintainer of the box so > that this issue can be fixed. > > unexpected token at '<!DOCTYPE html><html lang="en-us"><head> > <meta charset="utf-8"> > <title>HashiCorp Cloud Platform</title> > <meta name="description" content=""> > (...) > </body></html> > ``` > > The full error output contains an HTML page that I wall paste at the very > bottom of this bug report as to keep the actual text readable. > > I've encountered this error before for an older version, and I had to remove > the box and download a fresh copy of it to upgrade to the version that is > currently installed on my system. > > The host system is: > - Linux Mint 21.3 > - Vagrant 2.4.3 > - Virtualbox 7.1.4-165100~Ubuntu~jammy amd64 > Even though the host system is not Debian, I'm reporting this issue here, > because it's about a Debian Vagrant Box. If this is not correct, please tell > me and I'll try someplace else.
This is not a problem with the Debian box. This is a problem with the Hashicorp Cloud Platform (HCP), formerly "Vagrant Cloud", that hosts Vagrant boxes. HCP changed its API without prior notice. They won't fix it. In your case, you are already using the non-free version of Vagrant (2.4+). So you just need to remove the box (vagrant box remove debian/bookworm64) and re-add it. It will download a version that no longer points to the old URL. Alternatively, the problem was also fixed in version 2.3.4+dfsg-1+deb12u1 (Debian 12, available in proposed-updates). Best, Lucas
