Skip to content

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

Open
@unfulvio

Description

@unfulvio

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions