Description of problem: When I try to use Vagrant on Mageia 7, it dies with a dependency error with the childprocess rubygem as follows: [ngompa@mgagnome-skuld-vm ~]$ vagrant up Traceback (most recent call last): 8: from /usr/share/vagrant/gems/bin/vagrant:23:in `<main>' 7: from /usr/share/rubygems/rubygems.rb:300:in `activate_bin_path' 6: from /usr/share/rubygems/rubygems.rb:300:in `synchronize' 5: from /usr/share/rubygems/rubygems.rb:300:in `block in activate_bin_path' 4: from /usr/share/rubygems/rubygems/specification.rb:1413:in `activate' 3: from /usr/share/rubygems/rubygems/specification.rb:1431:in `activate_dependencies' 2: from /usr/share/rubygems/rubygems/specification.rb:1431:in `each' 1: from /usr/share/rubygems/rubygems/specification.rb:1442:in `block in activate_dependencies' /usr/share/rubygems/rubygems/dependency.rb:310:in `to_specs': Could not find 'childprocess' (~> 0.6.0) - did find: [childprocess-1.0.1] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/usr/share/gems:/usr/share/vagrant/gems:/home/ngompa/.vagrant.d/gems', execute `gem env` for more information Version-Release number of selected component (if applicable): 2.0.4-1.mga7 How reproducible: Always Steps to Reproduce: 1. Install fresh Mageia 7 2. “su -c ‘dnf install vagrant virtualbox’” 3. “vagrant up” with a Vagrantfile
any vagrant command output the same message, for example "vagrant help" the gem childprocess is installed as an rpm dependency by ruby-childprocess-1.0.1-1.mga7.noarch but installed gem versions are quite more recent than requisites from /usr/share/vagrant/gems/specifications/vagrant-2.0.4.gemspec The current version of vagrant is 2.2.26 and the rpm provided on the vagrant site ( https://releases.hashicorp.com/vagrant/2.2.6/vagrant_2.2.6_x86_64.rpm) works well on mageia 7
CC: (none) => eric.gerbier
i can try to update vagrant to 2.2.6.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Resolution: (none) => OLDStatus: NEW => RESOLVED