Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#68024 - [vagrant] ruby syntax error after upgrading to 2.2.10-2

Attached to Project: Community Packages
Opened by Graham Hay (grahamrhay) - Monday, 28 September 2020, 10:18 GMT
Last edited by Jonathan Steel (jsteel) - Monday, 26 October 2020, 08:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:


After upgrading from 2.2.9-2 to 2.2.10-2, I got a ruby syntax error from any vagrant command:

```
$ vagrant up
Ignoring bcrypt_pbkdf-1.0.1 because its extensions are not built. Try: gem pristine bcrypt_pbkdf --version 1.0.1
Ignoring ed25519-1.2.4 because its extensions are not built. Try: gem pristine ed25519 --version 1.2.4
Ignoring ffi-1.13.1 because its extensions are not built. Try: gem pristine ffi --version 1.13.1
Ignoring unf_ext-0.0.7.7 because its extensions are not built. Try: gem pristine unf_ext --version 0.0.7.7
/opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/plugin/manager.rb:4:in `require_relative': /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/bundler.rb:243: syntax error, unexpected '.' (SyntaxError)
if solution_file&.valid?
^
/opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/bundler.rb:258: syntax error, unexpected '.'
if !solution_file&.valid?
^
/opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/bundler.rb:869: syntax error, unexpected keyword_end, expecting end-of-input
from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/plugin/manager.rb:4:in `<top (required)>'
from /home/graham/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /home/graham/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant.rb:40:in `<top (required)>'
from /home/graham/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:130:in `require'
from /home/graham/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:130:in `rescue in require'
from /home/graham/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:35:in `require'
from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/bin/vagrant:88:in `<main>'
```

Downgrading to 2.2.9-2 worked fine again
This task depends upon

Closed by  Jonathan Steel (jsteel)
Monday, 26 October 2020, 08:22 GMT
Reason for closing:  Not a bug
Comment by Jonathan Steel (jsteel) - Tuesday, 29 September 2020, 18:33 GMT
I cannot reproduce this. Could you share your Vagrantfile so I can try?
Comment by Graham Hay (grahamrhay) - Friday, 02 October 2020, 13:18 GMT
Sorry, this ended up in my spam folder.

> Could you share your Vagrantfile

Hmm, interesting, I hadn't considered that it could be that. I'll try with an example from the vagrant docs and, if that works, I'll comment some of mine out, and see if that helps. Thanks.
Comment by Graham Hay (grahamrhay) - Sunday, 25 October 2020, 11:36 GMT
I get the same error, calling `vagrant init` in an empty folder, so I don't think my vagrantfile is the problem
Comment by Jonathan Steel (jsteel) - Sunday, 25 October 2020, 13:35 GMT
It must be something about your setup though, as this works for me:

$ vagrant --version
Vagrant 2.2.10
$ mkdir test
$ cd test
$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.


If that's exactly what you are doing, then I cannot reproduce this. If you are doing something different then please share.
Comment by Graham Hay (grahamrhay) - Sunday, 25 October 2020, 20:16 GMT
I think it's a problem with RVM. Thanks.

Loading...