Created
June 2, 2020 10:41
-
-
Save elkoniu/ba74f7e71d5d2239455f67a18d9268a6 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $ vagrant | |
| Traceback (most recent call last): | |
| 8: from /usr/share/vagrant/gems/bin/vagrant:23:in `<main>' | |
| 7: from /usr/share/rubygems/rubygems.rb:303:in `activate_bin_path' | |
| 6: from /usr/share/rubygems/rubygems.rb:303:in `synchronize' | |
| 5: from /usr/share/rubygems/rubygems.rb:304:in `block in activate_bin_path' | |
| 4: from /usr/share/rubygems/rubygems/specification.rb:1420:in `activate' | |
| 3: from /usr/share/rubygems/rubygems/specification.rb:1438:in `activate_dependencies' | |
| 2: from /usr/share/rubygems/rubygems/specification.rb:1438:in `each' | |
| 1: from /usr/share/rubygems/rubygems/specification.rb:1449:in `block in activate_dependencies' | |
| /usr/share/rubygems/rubygems/dependency.rb:313:in `to_specs': Could not find 'net-ssh' (~> 5.1.0) - did find: [net-ssh-5.2.0] (Gem::MissingSpecVersionError) | |
| Checked in 'GEM_PATH=/usr/share/gems:/usr/share/vagrant/gems:/home/ppolawsk/.vagrant.d/gems', execute `gem env` for more information |
No problem. I have already reported this to Fedora package maintainers,
last time I checked fix was ready to roll out. I guess it is mater of days
when it will be working fine again.
sob., 6 cze 2020, 14:30 użytkownik MG40 <[email protected]> napisał:
… ***@***.**** commented on this gist.
------------------------------
Thank you very much for your reply. Got it running. But it looks like I
have to stall any updates :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://gist.github.com/ba74f7e71d5d2239455f67a18d9268a6#gistcomment-3332421>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARUPLD5WTET7Z3D6BXC7KLRVIZETANCNFSM4NTDKF3Q>
.
Thank you for taking to repoty and also for your message. I see a new release but not sure whether I should go ahead and give it a try.
I think it is fixed now. I just updated my fedora 31 and vagrant is working fine with rubygem-net-ssh-5.2:
[ppolawsk@chopper]<~>$ sudo rpm -qa | grep rubygem-net-ssh
rubygem-net-ssh-5.2.0-1.fc31.noarch
[ppolawsk@chopper]<~>$ sudo rpm -qa | grep vagrant
vagrant-2.2.9-1.fc31.noarch
vagrant-libvirt-0.0.45-3.fc31.noarch
Yes. Saw that and updated :)
It works! Thank you for your effort.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you very much for your reply. Got it running. But it looks like I have to stall any updates :)