Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with unmet dependencies with Fedora 31 and Vagrant 2.2.6 (has workaround) #185

Open
unfulvio opened this issue Jan 2, 2020 · 0 comments
Labels

Comments

@unfulvio
Copy link

unfulvio commented Jan 2, 2020

I ran into the following issue after updating to Fedora 31 from Fedora 30. I was running Vagrant 2.2.5 and then updated contextually to 2.2.6.

When doing a vagrant up, Vagrant threw some error about plugins needing attention, so I tried first to repair. That wasn't enough so I tried to reinstall - at that point I got this error:

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 listen (~> 3.0.0) and listen (= 3.1.5)
  Activated listen-3.1.5
  which does not match conflicting dependency (~> 3.0.0)

  Conflicting dependency chains:
    listen (= 3.1.5), 3.1.5 activated

  versus:
    middleman-core (= 4.2.1), 4.2.1 activated, depends on
    listen (~> 3.0.0)

I am not sure who introduced that dependency but the only way I could solve it was to re-install the plugin with:

$ VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install vagrant-hostsupdater

The VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 made it pass.

Perhaps this is something you should be aware of.

Thank you and happy new year

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants