Your message dated Mon, 26 Mar 2018 19:36:17 +0000 with message-id <e1f0xuj-0007oi...@fasolo.debian.org> and subject line Bug#890662: fixed in vagrant 2.0.2+dfsg-3 has caused the Debian Bug report #890662, regarding vagrant: Depends on incompatible version of ruby-net-ssh to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 890662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: vagrant Version: 2.0.2+dfsg-2 Severity: normal Tags: patch Dear Maintainer, After upgrading vagrant from version 1.9.1+dfsg-1 to 2.0.2+dfsg-2 on my stretch machine, I tried running "vagrant up" only to find that my box could not be started due to an invalid option for ruby-net-ssh: ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key ==> default: Forcing shutdown of VM... ==> default: Destroying VM and associated drives... /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' When troubleshooting this, I found bug #884104 and learned that I needed a newer version of ruby-net-ssh, since my installed version (3.2.0-1) did not support the option :verify_host_key. Installing version 4.2.0-2 fixed the problem. Please update the dependency on ruby-net-ssh to at least version 4.2.0. A simple patch is attached. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (110, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vagrant depends on: ii bsdtar 3.2.2-2 ii curl 7.52.1-5+deb9u4 ii openssh-client 1:7.4p1-10+deb9u2 ii ruby 1:2.3.3 ii ruby-childprocess 0.5.9-1 ii ruby-erubis 2.7.0-3 ii ruby-i18n 0.7.0-2 ii ruby-listen 3.0.3-3 ii ruby-log4r 1.1.10-4 ii ruby-net-scp 1.2.1-4 ii ruby-net-sftp 1:2.1.2-3 ii ruby-net-ssh 1:4.2.0-2 ii ruby-rest-client 1.8.0-3 Versions of packages vagrant recommends: pn vagrant-libvirt <none> Versions of packages vagrant suggests: pn virtualbox <none> -- no debconf information--- debian/control.org 2018-02-17 14:06:27.721979518 +0100 +++ debian/control 2018-02-17 14:07:03.762463733 +0100 @@ -14,7 +14,7 @@ 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 @@ 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}
--- End Message ---
--- Begin Message ---Source: vagrant Source-Version: 2.0.2+dfsg-3 We believe that the bug you reported is fixed in the latest version of vagrant, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro <terce...@debian.org> (supplier of updated vagrant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Mon, 26 Mar 2018 16:14:19 -0300 Source: vagrant Binary: vagrant Architecture: source Version: 2.0.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Description: vagrant - Tool for building and distributing virtualized development enviro Closes: 890662 Changes: vagrant (2.0.2+dfsg-3) unstable; urgency=medium . * Specify minimal version of ruby-net-ssh required (Closes: #890662) Checksums-Sha1: ddf5547db22c71e4699904d01b5f06b7dc3c139a 2296 vagrant_2.0.2+dfsg-3.dsc bc7dd19cf18fb56d1bb399561ca75f685f98c017 12112 vagrant_2.0.2+dfsg-3.debian.tar.xz ade58ede541b32dfbec5f4e201ce25af1c4f5cf8 7185 vagrant_2.0.2+dfsg-3_source.buildinfo Checksums-Sha256: ef7896fb0ce9d8e03c0c210f833b2989a348fa3f4845b28d219514e63baa6191 2296 vagrant_2.0.2+dfsg-3.dsc 58bf79f7c8a4fad6dc4fe1a0a9ceba520605bc6b61d2ec16328b6eb16aa6592c 12112 vagrant_2.0.2+dfsg-3.debian.tar.xz b04fbce7b3f3b70a5f3df6e1e5b6fb334eef44f7882a4d9e006d1516f0ecada6 7185 vagrant_2.0.2+dfsg-3_source.buildinfo Files: b2bf9720bd7c8eb927c57d4ad6c9bd6c 2296 admin optional vagrant_2.0.2+dfsg-3.dsc 377e64b87458cf5eea8aaf65eeb5dc44 12112 admin optional vagrant_2.0.2+dfsg-3.debian.tar.xz 3aceae166abcb4fa2b903c12c9d90557 7185 admin optional vagrant_2.0.2+dfsg-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq5RyEACgkQ/A2xu81G C96hKQ/+NVTTCxLaG7hoUc4i+bPP7D++FsCuXDKYB8CzK7aDrI8TrFduUYfH7po5 WqvNPNAfNYD5YkuuIDN1/AMh6O5+9D2mpAiOWPg4MXbfxaXtEINWQQJOGeVz/XdI 0f6fVYH2Rl+vkmC7uSrqamsQo4O4sPzzZvVyEIMvl6+gP677/eIBFzdE2/QpVDrv MnTgO3A6qprS0egJZWIRVyBm1D6a824CJsK7L6l2rDtvkrr0zKdpTGPFip3pfp3v HF2evRbX/3YNgC6b0JUJTHX/XHLhIE7E81kQvaEu3wZVORgT1+YiFMn6V8WQmJJF zKUy2WCQmjcCd7zui/5f1iEs3ECcaWf96ykQms+rWMXP/5x7G+Eh6Thh0wZLkk5w N9WV5NzHg1wcLq2ktpt6gQ+Ap4RshkXpw043FG1VbCSh8iXArrFfqd5hsawZHt2n yPojUe+/V1Q+NcCsYQrztKCb0r/7yg+r1/bHwpLCI9PCEQMFrNIE7p2SNiuLIvrK CWy3BD0q3TaLsTP1ti0TfGvhgl9RRo+FLCPDKsTKbqiz4J5r2+WqpEbjVfcVioY8 LCwBQQ1DWsBQG9ds9HPKbGYDb6wvFJ5u2KrXHrLK6TVrNX5yAmZj2l7b94FHIyjJ b4GtvLa2bNbKMwqT/FA7F6Q499i/917QqS07MDhhfQAg3ykNmwA= =HM0S -----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
