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#65451 - [vagrant] Still incompatible with ruby >= 2.7

Attached to Project: Community Packages
Opened by Mark Stenglein (ocelotsloth) - Tuesday, 11 February 2020, 02:23 GMT
Last edited by Jonathan Steel (jsteel) - Monday, 06 April 2020, 19:15 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jonathan Steel (jsteel)
Anatol Pomozov (anatolik)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

Vagrant is not technically compatible with ruby version 2.7, which was introduced last month.

See the gemspec: https://github.com/hashicorp/vagrant/blob/58687e6c4485790670fead7b579e3a1a60927b77/vagrant.gemspec#L15

s.required_ruby_version = "~> 2.4", "< 2.7"

I'm not sure if there's a way to address this without downgrading the version of ruby installed but it displays a significant number of deprecation warnings as-is.


Additional info:
* package version(s):
- Vagrant 2.2.7
- Ruby: ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux]
* config and/or log files etc.

❯ vagrant -h
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /opt/vagrant/embedded/gems/gems/vagrant-2.2.7/lib/vagrant/bundler.rb:428.
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /opt/vagrant/embedded/gems/gems/vagrant-2.2.7/lib/vagrant/bundler.rb:428.
/opt/vagrant/embedded/gems/gems/vagrant-2.2.7/plugins/kernel_v2/config/vm.rb:379: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/opt/vagrant/embedded/gems/gems/vagrant-2.2.7/plugins/kernel_v2/config/vm_provisioner.rb:95: warning: The called method `add_config' is defined here
/opt/vagrant/embedded/gems/gems/vagrant-2.2.7/lib/vagrant/errors.rb:103: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/opt/vagrant/embedded/gems/gems/i18n-1.8.2/lib/i18n.rb:195: warning: The called method `t' is defined here
(eval):3: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/opt/vagrant/embedded/gems/gems/vagrant-2.2.7/lib/vagrant/ui.rb:223: warning: The called method `say' is defined here
Usage: vagrant [options] <command> [<args>]

-v, --version Print the version and exit.
-h, --help Print this help.

Common commands:
box manages boxes: installation, removal, etc.
cloud manages everything related to Vagrant Cloud
destroy stops and deletes all traces of the vagrant machine
global-status outputs status Vagrant environments for this user
halt stops the vagrant machine
help shows the help for a subcommand
init initializes a new Vagrant environment by creating a Vagrantfile
login
package packages a running vagrant environment into a box
plugin manages plugins: install, uninstall, update, etc.
port displays information about guest port mappings
powershell connects to machine via powershell remoting
provision provisions the vagrant machine
push deploys code in this environment to a configured destination
rdp connects to machine via RDP
reload restarts vagrant machine, loads new Vagrantfile configuration
resume resume a suspended vagrant machine
snapshot manages snapshots: saving, restoring, etc.
ssh connects to machine via SSH
ssh-config outputs OpenSSH valid configuration to connect to the machine
status outputs status of the vagrant machine
suspend suspends the machine
up starts and provisions the vagrant environment
upload upload to machine via communicator
validate validates the Vagrantfile
version prints current and latest Vagrant version
winrm executes commands on a machine via WinRM
winrm-config outputs WinRM configuration to connect to the machine

For help on any individual command run `vagrant COMMAND -h`

Additional subcommands are available, but are either more advanced
or not commonly used. To see all subcommands, run the command
`vagrant list-commands`.



* link to upstream bug report, if any

https://github.com/hashicorp/vagrant/issues/11290
https://github.com/hashicorp/vagrant/issues/11290#issuecomment-571360711

Steps to reproduce:

Install vagrant. Run any vagrant command such as `vagrant -h`.
This task depends upon

Closed by  Jonathan Steel (jsteel)
Monday, 06 April 2020, 19:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  vagrant 2.2.7-3: Add fix for ruby27 warnings
Comment by Mark Stenglein (ocelotsloth) - Tuesday, 11 February 2020, 02:27 GMT
That github issue had a link to the gemspec file. It was linked to a commit rather than the actual v2.2.7 tag.

Here is the appropriate link: https://github.com/hashicorp/vagrant/blob/v2.2.7/vagrant.gemspec#L15

Loading...