Le 12/04/2021 à 13:14, Christopher Huhn a écrit : > Package: cloud.debian.org > Severity: serious > > The latest Buster libvirt image for vagrant gives me a 404, `vagrant box > update` fails. > > λ > curl > https://app.vagrantup.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box
Hi Thanks for your interest for the Debian Vagrant boxes. when I'm doing vagrant box update the box is downloaded from https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409./providers/libvirt.box and is properly found vagrant box update ==> default: Checking for updates to 'debian/buster64' default: Latest installed version: 10.4.0 default: Version constraints: default: Provider: libvirt ==> default: Updating 'debian/buster64' with provider 'libvirt' from version ==> default: '10.4.0' to '10.20210409.1'... ==> default: Loading metadata for box 'https://vagrantcloud.com/debian/buster64' ==> default: Adding box 'debian/buster64' (v10.20210409.1) for provider: libvirt default: Downloading: https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com ==> default: Successfully added box 'debian/buster64' (v10.20210409.1) for 'libvirt'! when creating a fresh environment with export VAGRANT_DEFAULT_PROVIDER=libvirt vagrant init debian/buster64` vagrant up is the box properly downloaded on your side ? -- You know an upstream is nice when they even accept m68k patches. - John Paul Adrian Glaubitz, Debian OpenJDK maintainer