$ vagrant box add prec output/2015-02-19/vagrant-lxc-precise-amd64.box Vagrant experienced a version conflict with some installed plugins! This usually happens if you recently upgraded Vagrant. As part of the upgrade process, some existing plugins are no longer compatible with this version of Vagrant. The recommended way to fix this is to remove your existing plugins and reinstall them one-by-one. To remove all plugins: rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems Note if you have an alternate VAGRANT_HOME environmental variable set, the folders above will be in that directory rather than your user's home directory. The error message is shown below: Could not find gem 'net-sftp (~> 2.1) ruby', which is required by gem 'vagrant (>= 0) ruby', in any of the sources. $ vagrant box add prec output/2015-02-19/vagrant-lxc-precise-amd64.box Vagrant experienced a version conflict with some installed plugins! This usually happens if you recently upgraded Vagrant. As part of the upgrade process, some existing plugins are no longer compatible with this version of Vagrant. The recommended way to fix this is to remove your existing plugins and reinstall them one-by-one. To remove all plugins: rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems Note if you have an alternate VAGRANT_HOME environmental variable set, the folders above will be in that directory rather than your user's home directory. The error message is shown below: Could not find gem 'rest-client (< 2.0, >= 1.6.0) ruby', which is required by gem 'vagrant (>= 0) ruby', in any of the sources. After installing 'rubygem-rest-client' and 'rubygem-net-sftp' all works fine.
Hi Igor, This should be fixed in vagrant-1.7.2-2 [1]. Could you please confirm? [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=19808
(In reply to Vít Ondruch from comment #1) > Hi Igor, > > This should be fixed in vagrant-1.7.2-2 [1]. Could you please confirm? > > > [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=19808 not fully, but it's fixed in git: http://pkgs.fedoraproject.org/cgit/vagrant.git/commit/?id=eec12431c58f0638990f4895c13a059fb33b697f http://pkgs.fedoraproject.org/cgit/vagrant.git/commit/?id=f0f8a70da5fd42d247afd6aa5c8f822ea724a7aa Then let's set status to POST
vagrant-1.7.2-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/vagrant-1.7.2-2.fc21
vagrant-1.7.2-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/vagrant-1.7.2-3.fc21
Package vagrant-1.7.2-3.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vagrant-1.7.2-3.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2341/vagrant-1.7.2-3.fc21 then log in and leave karma (feedback).
vagrant-1.7.2-3.fc21.1 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/vagrant-1.7.2-3.fc21.1
vagrant-1.7.2-3.fc21.1 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.