Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use that. However, it fails. Can you please
investigate the situation and fix it? I copied some of the output at the
bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing, but because machine-isolation
support by ci.debian.net is new I have not marked this bug as serious (yet).

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vagrant-lxc/44891490/log.gz

  67s autopkgtest [06:06:56]: test basics: [-----------------------
  67s + export VAGRANT_DEFAULT_PROVIDER=lxc
  67s + debian-distro-info --stable
  67s + release=bookworm
  67s + box=debian/bookworm64
  67s + [ -z /tmp/autopkgtest.h1pgtq/autopkgtest_tmp ]
  67s + grep -q lxc.network.type.*veth /etc/lxc/default.conf
  67s + echo USE_LXC_BRIDGE=true
  67s + systemctl restart lxc-net
  67s + cat
  67s + vagrant box list
  67s + grep debian/bookworm64
  68s + vagrant box add --force --provider=lxc debian/bookworm64
  69s ==> box: Loading metadata for box 'debian/bookworm64'
  69s     box: URL: https://vagrantcloud.com/debian/bookworm64
  70s The box you're attempting to add doesn't support the provider
  70s you requested. Please find an alternate box or use an alternate
  70s provider. Double-check your requested provider to verify you didn't
  70s simply misspell it.
  70s
  70s If you're adding a box from HashiCorp's Vagrant Cloud, make sure
the box is
  70s released.
  70s
  70s Name: debian/bookworm64
  70s Address: https://vagrantcloud.com/debian/bookworm64
  70s Requested provider: ["lxc"]
  70s autopkgtest [06:06:59]: test basics: -----------------------]