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

Fedora 29: various conflicts #171

Open
stefangweichinger opened this issue Nov 1, 2018 · 2 comments
Open

Fedora 29: various conflicts #171

stefangweichinger opened this issue Nov 1, 2018 · 2 comments

Comments

@stefangweichinger
Copy link

vagrant plugin install vagrant-hostsupdater
Installing the 'vagrant-hostsupdater' plugin. This can take a few minutes...
/usr/share/gems/gems/psych-3.0.2/lib/psych.rb:232: warning: already initialized constant Psych::LIBYAML_VERSION
/usr/share/ruby/psych.rb:232: warning: previous definition of LIBYAML_VERSION was here
/usr/share/gems/gems/psych-3.0.2/lib/psych.rb:234: warning: already initialized constant Psych::FALLBACK
/usr/share/ruby/psych.rb:234: warning: previous definition of FALLBACK was here
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies vagrant-hostsupdater (= 1.0.1) and vagrant-hostsupdater (= 1.0.2)
  Activated vagrant-hostsupdater-1.0.2
  which does not match conflicting dependency (= 1.0.1)

  Conflicting dependency chains:
    vagrant-hostsupdater (= 1.0.2), 1.0.2 activated

  versus:
    vagrant-hostsupdater (= 1.0.1)

  Gems matching vagrant-hostsupdater (= 1.0.1):
    vagrant-hostsupdater-1.0.1

how to get rid of that?

I tried removing/uninstalling all plugins and/or vagrant itself, how to proceed here?

@cgsmith
Copy link
Collaborator

cgsmith commented Jul 9, 2019

I'll test this out locally.

@cgsmith cgsmith added the bug label Jul 9, 2019
@talheim-it
Copy link

@cgsmith

Same on Fedora 33:
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 racc (= 1.4.16) and racc (= 1.5.1)
Activated racc-1.5.1
which does not match conflicting dependency (= 1.4.16)

Conflicting dependency chains:
racc (= 1.5.1), 1.5.1 activated

versus:
racc (= 1.4.16)

Gems matching racc (= 1.4.16):
racc-1.4.16

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

No branches or pull requests

3 participants