Package: vagrant Version: 1.8.1+dfsg-1 Followup-For: Bug #818237 Hello,
i looked into this issue and found the following discussion: https://github.com/pradels/vagrant-libvirt/issues/575 which led me to: https://github.com/rubygems/rubygems/commit/044b0e2685e4b219b013f1067d670918a48c1f62 I can confirm that editing /usr/lib/ruby/2.3.0/rubygems/specification.rb as suggested fixes the issue at hand. This issue therefore seems to be with rubygems rather than vagrant itself. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf-8, LC_CTYPE=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.1.2-11+b1 ii bundler 1.11.2-1 ii curl 7.47.0-1 ii openssh-client 1:7.2p2-2 ii ruby 1:2.3.0+1 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-3 ii ruby-net-sftp 1:2.1.2-3 ii ruby-net-ssh 1:3.0.1-3 ii ruby-nokogiri 1.6.7.2-3 ii ruby-rb-inotify 0.9.7-1 ii ruby-rest-client 1.8.0-2 vagrant recommends no packages. Versions of packages vagrant suggests: ii virtualbox 5.0.16-dfsg-2 -- no debconf information
