Conversation
|
Skipping CI for Draft Pull Request. |
Signed-off-by: Maksym Pavlenko <pavlenko.maksym@gmail.com>
| sudo apt-get build-dep -y ruby-libvirt | ||
| sudo apt-get install -y --no-install-recommends libxslt-dev libxml2-dev libvirt-dev ruby-bundler ruby-dev zlib1g-dev | ||
| sudo vagrant plugin install vagrant-libvirt | ||
| sudo env VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install vagrant-libvirt |
There was a problem hiding this comment.
nit: would be good to have a comment referring to why this was added.
|
/cherrypick release/2.0 |
|
@mxpv: new pull request created: #11739 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mxpv: new pull request created: #11740 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Vagrant setup is broken in all branches due to dependency resolution conflict:
$ vagrant plugin install vagrant-libvirt ... Installing the 'vagrant-libvirt' plugin. This can take a few minutes... 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 csv (= 3.2.8) and csv (= 3.3.4) Activated csv-3.3.4 which does not match conflicting dependency (= 3.2.8) Conflicting dependency chains: csv (= 3.3.4), 3.3.4 activated versus: csv (= 3.2.8) Gems matching csv (= 3.2.8): csv-3.2.8The workaround suggested in hashicorp/vagrant#13510 (comment) seems to work.