Arch Linux

mbork

Member

Registered: 2019-01-04

Posts: 24

Vagrant plugins broke after the latest update

Hi all,

I've updated my system (using `sudo pacman -Syu`) yesterday, and after the update my Vagrant installation broke. When I say `vagrant plugin install vagrant-notify-forwarder`, I get this:

Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:

conflicting dependencies bigdecimal (= 3.1.3) and bigdecimal (= 3.1.8)
  Activated bigdecimal-3.1.8
  which does not match conflicting dependency (= 3.1.3)

  Conflicting dependency chains:
    bigdecimal (= 3.1.8), 3.1.8 activated

  versus:
    bigdecimal (= 3.1.3)

  Gems matching bigdecimal (= 3.1.3):
    bigdecimal-3.1.3

Anybody encountered this? Any hints? I tried reinstalling `vagrant` and downgrading it, both to no effect...

mbork

Member

Registered: 2019-01-04

Posts: 24

Re: Vagrant plugins broke after the latest update

Answering myself: I found this setting helped: VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 (source: https://warlord0blog.wordpress.com/2024 … -updates/)

However, due to a breaking change in Ruby (https://stackoverflow.com/a/75353113) the plugin could not be loaded. I needed to edit `~/.vagrant.d/gems/3.2.5/gems/vagrant-notify-0.6.1/lib/vagrant-notify.rb` and fix the method name manually.

Last edited by mbork (2024-09-04 04:01:53)

Segaja

Package Maintainer (PM)

Registered: 2011-01-02

Posts: 14

Website

Re: Vagrant plugins broke after the latest update

Thanks for bringing this to our attention. I have opened https://gitlab.archlinux.org/archlinux/ … -/issues/3 to track this as it clearly is a packaging issue.

I have already identified the source issue already and started to work against fixing it already in https://gitlab.archlinux.org/archlinux/ … requests/1 but it might take some time to get this solved completely.

sorcix

Member

Registered: 2010-10-22

Posts: 8

Website

Re: Vagrant plugins broke after the latest update

Looks like this now affects the vagrant_cloud plugin that's installed by default, causing Vagrant to break even when not using plugins.

❯ vagrant version
/usr/lib/ruby/3.2.0/rubygems/specification.rb:2303:in `raise_if_conflicts': Unable to activate vagrant_cloud-3.1.1, because rexml-3.3.2 conflicts with rexml (~> 3.2.5) (Gem::ConflictError)
        from /usr/lib/ruby/3.2.0/rubygems/specification.rb:1432:in `activate'
        from /usr/lib/ruby/3.2.0/rubygems/core_ext/kernel_gem.rb:63:in `block in gem'
        from /usr/lib/ruby/3.2.0/rubygems/core_ext/kernel_gem.rb:63:in `synchronize'
        from /usr/lib/ruby/3.2.0/rubygems/core_ext/kernel_gem.rb:63:in `gem'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/bin/vagrant:95:in `block (2 levels) in <main>'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/bin/vagrant:94:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/bin/vagrant:94:in `block in <main>'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/bin/vagrant:105:in `<main>'

The environment variable mbork suggested no longer works in this case.

I also tried to remove the vagrant_cloud gem from /opt/vagrant, but vagrant seems to require it.

Edit: I could make it work by changing the rexml version requirement in /opt/vagrant/embedded/gems/specifications/vagrant_cloud-3.1.1.gemspec

Last edited by sorcix (2024-09-16 09:01:01)

jblouvet

Member

Registered: 2024-10-03

Posts: 1

Re: Vagrant plugins broke after the latest update

Edit: I could make it work by changing the rexml version requirement in /opt/vagrant/embedded/gems/specifications/vagrant_cloud-3.1.1.gemspec

I also could make vagrant run by editing this file, but it cannot run virtualbox virtual machines as it requires virtualbox up to 7.0, an the current installed version is 7.1. I tried to manually downgrade virtualbox with

sudo pacman -U virtualbox-7.0.8-2-x86_64.pkg.tar.zst virtualbox-host-dkms-7.0.8-2-x86_64.pkg.tar.zst

(In /var/cache/pacman/pkg), but it makes virtualbox crash with the code NS_ERROR_FAILURE (0x80004005).

xerxes_

Member

Registered: 2018-04-29

Posts: 815

Re: Vagrant plugins broke after the latest update

@jblouvet see here: https://bbs.archlinux.org/viewtopic.php … 3#p2199183