Arch Linux

opaldes

Member

Registered: 2022-12-07

Posts: 3

Update breaking dependencies, how to avoid or circumvent for vagrant

Hi,
I ran now multiple times into issues with vagrant and virtualbox, where the newest version of virtual box provided is not compatible with the newest version of vagrant.
Currently I circumvent the issue by building vagranty locally, my question would be is there a better way to manage vagrant?
For the future I would like to be use pacman again for vagrant.

Last edited by opaldes (2022-12-07 09:19:58)

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,132

Re: Update breaking dependencies, how to avoid or circumvent for vagrant

https://bbs.archlinux.org/viewtopic.php?id=57855

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

opaldes

Member

Registered: 2022-12-07

Posts: 3

Re: Update breaking dependencies, how to avoid or circumvent for vagrant

I added further info to the main post, but basicly the newest version of virtualbox 7.0+ is not compatible with the provided vagrant version from the repository.
Would like to prevent this in the future and would like to know if there is a way to not build from source in the future.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,919

Re: Update breaking dependencies, how to avoid or circumvent for vagrant

current version of vagrant in repos appears to be the latest released version, also https://developer.hashicorp.com/vagrant … virtualbox mentions virtualbox 6.1 as highest supported version .

Are you stuck with the virtualbox / vagrant combo or can you switch either to something else ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

opaldes

Member

Registered: 2022-12-07

Posts: 3

Re: Update breaking dependencies, how to avoid or circumvent for vagrant

Currently I cant switch either, and I am fine with building from source.
I would just like to know if there were any best practices to prevent version bumps, just sucks that my setups dont work after an upgrade, and if there is a way to still use reliably pacman.
I tried to use qemu, but had errors requiring virtualbox.

seth

Member

Registered: 2012-09-03

Posts: 51,165

Re: Update breaking dependencies, how to avoid or circumvent for vagrant

https://bbs.archlinux.org/viewtopic.php?id=57855

circumvent the issue by building vagranty locally

vagrant upstream is at 2.3.3, like the repo version - what do you actually build locally?
According to the vagrnat changelog, "support for VirtualBox 7.0" was added w/ 2.3.2 so right now it's not even clear why you may have nor what kind of problems - what makes it impossible to suggest to avoid them.
There's no whatsoever indication that the repo vagrant and virtualbox releases are somehow incompatible and you've not provided any details on why you think they are.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc