Package: libruby2.1
Version: 2.1.5-2+deb8u2
Severity: important

One of the last updates to libruby2.1 has broken vagrant 1.6.5 ability to 
install/update plugins, the problem lies in rubygems.
vagrant plugin update as well as vagrant plugin install xyz does not work 
anymore because of this. 
The following error occurs:
$ vagrant plugin update 
Updating installed plugins...
/usr/local/lib/site_ruby/2.1.0/rubygems/specification.rb:946:in `all=': 
undefined method `group_by' for nil:NilClass (NoMethodError)
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in 
`with_isolated_gem'
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in 
`internal_install'
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:144:in `update'
        from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:111:in 
`update_plugins'
        from 
/usr/share/vagrant/plugins/commands/plugin/action/update_gems.rb:23:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in 
run'
        from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
        from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in 
`action'
        from /usr/share/vagrant/plugins/commands/plugin/command/update.rb:23:in 
`execute'
        from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in 
`execute'
        from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
        from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:258:in `cli'
        from /usr/bin/vagrant:173:in `<main>'

This error is known to vagrant 1.6.5, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817014
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818237

It is also known upstream:
rubygems (March 2015): 
https://github.com/rubygems/rubygems/commit/044b0e2685e4b219b013f1067d670918a48c1f62
vagrant (January 2016): https://github.com/mitchellh/vagrant/issues/6911 -> 
recommends newer vagrant version

Possible solutions imho:
- Fix rubygems in libruby2.1
- Fix vagrant 1.6.5
- Update jessie's vagrant to stretch's version
- backport stretch's vagrant to jessie-backports

This also opens possibile security problems due to installed vagrant plugins 
can not be updated anymore and are stuck at the installed version.

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libruby2.1 depends on:
ii  libc6         2.19-18+deb8u3
ii  libffi6       3.1-2+b2
ii  libgdbm3      1.8.3-13.1
ii  libgmp10      2:6.0.0+dfsg-6
ii  libncurses5   5.9+20140913-1+b1
ii  libreadline6  6.3-8+b3
ii  libssl1.0.0   1.0.1k-3+deb8u4
ii  libtinfo5     5.9+20140913-1+b1
ii  libyaml-0-2   0.1.6-3
ii  zlib1g        1:1.2.8.dfsg-2+b1

libruby2.1 recommends no packages.

libruby2.1 suggests no packages.

-- no debconf information

Reply via email to