[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted vagrant 2.0.2+dfsg-2~bpo9+1 (source all) into stretch-backports, stretch-backports



On Mon, Mar 26, 2018 at 04:29:05PM +0200, Sven Hoexter wrote:
> /usr/lib/ruby/vendor_ruby/net/ssh.rb:204:in `start': invalid option(s): verify_host_key (ArgumentError)
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:409:in `block (2 levels) in connect'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:383:in `block in connect'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:382:in `connect'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:83:in `block in wait_for_ready'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
> 	from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:61:in `wait_for_ready'
> 	from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890662

this is also an issue in buster with a partial upgrade from stretch.  I
just uploaded to unstable with only the fix for that, which should be
acceptable to fast-track into backports, and then you only need a
backport of ruby-net-ssh:

diff --git a/debian/changelog b/debian/changelog
index c653192..e89e910 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+vagrant (2.0.2+dfsg-3) unstable; urgency=medium
+
+  * Specify minimal version of ruby-net-ssh required (Closes: #890662)
+
+ -- Antonio Terceiro <terceiro@debian.org>  Mon, 26 Mar 2018 16:14:19 -0300
+
 vagrant (2.0.2+dfsg-2) unstable; urgency=medium

   * New upstream release.
diff --git a/debian/control b/debian/control
index 06c8800..7fd6312 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Build-Depends: bash-completion,
                ruby-log4r (>= 1.1.9),
                ruby-net-scp (>= 1.1.0),
                ruby-net-sftp,
-               ruby-net-ssh (>= 1:2.6.6),
+               ruby-net-ssh (>= 1:4.2.0),
                ruby-rest-client,
 Standards-Version: 4.1.3
 Vcs-Git: https://salsa.debian.org/ruby-team/vagrant.git
@@ -36,7 +36,7 @@ Depends: bsdtar,
          ruby-log4r (>= 1.1.9),
          ruby-net-scp (>= 1.1.0),
          ruby-net-sftp,
-         ruby-net-ssh (>= 1:2.6.6),
+         ruby-net-ssh (>= 1:4.2.0),
          ruby-rest-client,
          ${misc:Depends},
          ${shlibs:Depends}

Attachment: signature.asc
Description: PGP signature


Reply to: