Arch Linux

mbork

Member

Registered: 2019-01-04

Posts: 14

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: 14

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.