Gemfile/gemspec updates

Use new version of vagrant and vagrant-libvirt.

Don't version lock dev dependencies. Not sure why but this was
causing a lot of trouble.

Author: dustymabe

Gemfile

@@ -6,12 +6,12 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :ref => 'v1.8.6'
+  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :ref => 'v2.0.2'
 end
 
 group :plugins do
   gem "vagrant-sshfs" , path: "."
   # Add vagrant-libvirt plugin here, otherwise you won't be able to
   # use libvirt as a provider when you execute `bundle exec vagrant up`
-  gem "vagrant-libvirt" , '0.0.33'
+  gem "vagrant-libvirt" , '0.0.43'
 end

vagrant-sshfs.gemspec

@@ -23,9 +23,9 @@ Gem::Specification.new do |spec|
 
   spec.add_dependency 'win32-process'
 
-  spec.add_development_dependency 'bundler', '~> 1.7'
-  spec.add_development_dependency 'rake', '~> 10.0'
-  spec.add_development_dependency 'cucumber', '~> 2.1'
-  spec.add_development_dependency 'aruba', '~> 0.13'
-  spec.add_development_dependency 'komenda', '~> 0.1.6'
+  spec.add_development_dependency 'bundler'
+  spec.add_development_dependency 'rake'
+  spec.add_development_dependency 'cucumber'
+  spec.add_development_dependency 'aruba'
+  spec.add_development_dependency 'komenda'
 end