vagrant-vsphere 1.13.1 → 1.13.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a0d44c2157fc7b333b6c97c8a027386fb8f9db88
-  data.tar.gz: b1ba99bdba7b06d379f61a1ab55639b21491254b
+  metadata.gz: 8fe4d60f89f372adb57340679097c6eae9e210d9
+  data.tar.gz: 957d8893b8656a3448708454753ec7bee07807d7
 SHA512:
-  metadata.gz: aaced51e239e3d3567de2d783212a6c8e692e0158223cc21c2d15d2d6b6146b1c8feba6fe59270bf70983d4d410f8eb11e23c4c5988c42464d9bf17b04a3f4aa
-  data.tar.gz: 3b48f0aea570b3861ef2c286b4bd3d521d2e7840f1fc32eb8454c4773d3e690cf8da5d46276287779673d75dc64cb8ead6bad74a8dfc79069bbe64fd57de5967
+  metadata.gz: 6d5c30dc85efe858778bf29a9096e28fd2f2b4f3d914a9fdedd30862e2acc159f5162da71192ee3940d27ac9a7a3d363367da44f001d3af856f0163f185ed3cf
+  data.tar.gz: f122779c53c3934cad09b12f7efcfd61f242faf1dbe6b5fce265cf7e658520f9ae90ce52863ff3567b9105855e877ef8e3afc8a10db9990031ef1362f0aa609b

data/.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.13.1
+current_version = 1.13.2
 tag = true
 commit = true
 

data/CHANGELOG.md

@@ -1,4 +1,9 @@
-## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.0)
+## [1.13.2 (2017-12-06)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.2)
+
+  - Update rbvmomi dependency to v1.11.5 and greater (but still less than
+    2.0). v1.11.5 fixes the issue introduced in v1.11.4.
+
+## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.1)
 
   - Update rbvmomi dependency to avoid v1.11.4; something in
     [2725089](https://github.com/vmware/rbvmomi/commit/2725089a08312315c4eb85f13296fc159f50b4d1)

data/README.md

@@ -19,9 +19,9 @@ This provider is built on top of the
 * libxml2, libxml2-dev, libxslt, libxslt-dev
 
 ## Current Version
-**version: 1.13.1**
+**version: 1.13.2**
 
-vagrant-vsphere (**version: 1.13.1**) is available from
+vagrant-vsphere (**version: 1.13.2**) is available from
 [RubyGems.org](https://rubygems.org/gems/vagrant-vsphere)
 
 ## Installation

data/lib/vSphere/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module VSphere
-    VERSION = '1.13.1'
+    VERSION = '1.13.2'
   end
 end

data/vSphere.gemspec

@@ -14,12 +14,7 @@ Gem::Specification.new do |s|
   # force the use of Nokogiri 1.5.x to prevent conflicts with older versions of zlib
   s.add_dependency 'nokogiri', '~>1.5'
 
-  # force the use of at least rbvmomi 1.8.2 to work around concurrency errors:
-  # https://github.com/nsidc/vagrant-vsphere/issues/139
-  #
-  # rbvmomi v1.11.4 broke cloning VMs at NSIDC, see
-  # https://github.com/vmware/rbvmomi/issues/127
-  s.add_dependency 'rbvmomi', '>=1.8.2', '<1.11.4'
+  s.add_dependency 'rbvmomi', '>=1.11.5', '<2.0.0'
 
   s.add_dependency 'i18n', '>=0.6.4', '<=0.8.0'
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-vsphere
 version: !ruby/object:Gem::Version
-  version: 1.13.1
+  version: 1.13.2
 platform: ruby
 authors:
 - Andrew Grauch
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-12-05 00:00:00.000000000 Z
+date: 2017-12-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri
@@ -30,20 +30,20 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.2
+        version: 1.11.5
     - - "<"
       - !ruby/object:Gem::Version
-        version: 1.11.4
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.2
+        version: 1.11.5
     - - "<"
       - !ruby/object:Gem::Version
-        version: 1.11.4
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: i18n
   requirement: !ruby/object:Gem::Requirement