Hi,
On 07/11/24 at 16:41 +0100, Hinnack wrote:
> Hi,
>
> all boxes here: https://app.vagrantup.com/debian
> have no architecture assigned (unknown). Can that be changed?
This is now fixed for all boxes that are actively maintained (bullseye,
bookworm, testing)
> Are there any plans for adding a
Hi,
all boxes here: https://app.vagrantup.com/debian
have no architecture assigned (unknown). Can that be changed?
Are there any plans for adding arm64 boxes? VirtualBox is now supported on
Silicons Macs (libvirt was supported anyway)
kind regards,
Henrik
Hi,
all boxes here: https://app.vagrantup.com/debian
have no architecture assigned. Can you please change that?
Are there any plans for adding arm64 boxes? VirtualBox is now supported on
Silicons Macs (libvirt was supported any way)
kind regards,
Henrik
Note that the testing VM image is configured with apt pinning, so you
can install packages from unstable using e.g:
apt install gcc-snapshot/unstable
L.
On 06/10/19 at 09:47 -0500, Andrew Pennebaker wrote:
> My use case is getting some of the very latest applications in like qemu
> updates, t
My use case is getting some of the very latest applications in like qemu
updates, that aren't necessarily available in the testing repositories.
Hmm, maybe we could do a daily VM push and ignore broken states? This would be
a "best effort" artifact.
> On Oct 6, 2019, at 6:27 AM, Lucas Nussbaum
Hi,
On 12/07/19 at 20:15 -0500, Andrew Pennebaker wrote:
> Hey, neat that we have convenient VM's now for Debian! Could we get a VM
> for sid as well?
That's difficult, because unstable is frequently in a broken state...
What is your use case? (and why isn't it met by the testing64 and
contrib-te
Package: cloud.debian.org
Version: *
Hey, neat that we have convenient VM's now for Debian! Could we get a VM
for sid as well?
--
Cheers,
Andrew
