| View previous topic :: View next topic |
| Author |
Message |
gjy0724
Apprentice
Joined: 11 Jun 2005
Posts: 165
Location: Lock Haven, Pennsylvania
|
 Posted: Fri Sep 24, 2021 3:12 pm Post subject: [SOLVED] Update broke vagrant |
 |
|
Last night I updated one of my systems that I run vagrant on. This morning when I tried to run the app, I got the following error.
| Code: | $ vagrant 1 < 10:42:28
/usr/lib64/ruby/site_ruby/2.6.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'bcrypt_pbkdf' (~> 1.0.0) - did find: [bcrypt_pbkdf-1.1.0] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/home/vagrant/.gem/ruby/2.6.0:/usr/lib64/ruby/gems/2.6.0:/usr/local/lib64/ruby/gems/2.6.0', execute `gem env` for more information
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1446:in `block in activate_dependencies'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `each'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `activate_dependencies'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1417:in `activate'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems.rb:224:in `rescue in try_activate'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems.rb:217:in `try_activate'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:123:in `rescue in require'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require'
from /usr/lib64/ruby/gems/2.6.0/gems/vagrant-2.2.9/bin/vagrant:88:in `<main>'
/usr/lib64/ruby/site_ruby/2.6.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'bcrypt_pbkdf' (~> 1.0.0) - did find: [bcrypt_pbkdf-1.1.0] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/home/vagrant/.gem/ruby/2.6.0:/usr/lib64/ruby/gems/2.6.0:/usr/local/lib64/ruby/gems/2.6.0', execute `gem env` for more information
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1446:in `block in activate_dependencies'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `each'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `activate_dependencies'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/specification.rb:1417:in `activate'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems.rb:218:in `try_activate'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:123:in `rescue in require'
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require'
from /usr/lib64/ruby/gems/2.6.0/gems/vagrant-2.2.9/bin/vagrant:88:in `<main>'
/usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- vagrant (LoadError)
from /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib64/ruby/gems/2.6.0/gems/vagrant-2.2.9/bin/vagrant:88:in `<main>'
|
After some troubleshooting and determining that the bcrypt_pbkdf package was updated (from 1.0.0 to1.1.0-r1) , I decided to rollback, block the problem package, and re-update, which re-installed 1.0.0...thus solving my problem as vagrant is working again.
I am not sure if this is the right solution but I thought would at least post it hear. Let me know if I should create a bug for this build and I will do so, I see that there is a bug request to make the package stable (https://bugs.gentoo.org/813789).
I don't know if the issue is specifically with this package or another that has 1.0.0 of this package hardcoded.
Last edited by gjy0724 on Fri Sep 24, 2021 4:52 pm; edited 1 time in total |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30909
Location: here
|
| Posted: Fri Sep 24, 2021 3:44 pm Post subject: |
|
|
See bug #810715
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
gjy0724
Apprentice
Joined: 11 Jun 2005
Posts: 165
Location: Lock Haven, Pennsylvania
|
| Posted: Fri Sep 24, 2021 4:00 pm Post subject: |
|
|
Thank you,
It took me a while to figure out why I didn't see that bug listed when I searched for the package, but I searched for bcrypt_pbkdf instead of just bcrypt...hence I only received the ticket to stabilize 1.1.0-r1. So my solution was correct for now. |
|
| Back to top |
|
|
web.user
n00b
Joined: 14 May 2021
Posts: 17
|
| Posted: Sat Sep 25, 2021 1:47 pm Post subject: |
|
|
I solved it by running this:
| Code: | | gem install bcrypt_pbkdf -v 1.0.0 |
_________________
Check out ASN lookup tool to gather IP address information. |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30909
Location: here
|
| Posted: Sat Sep 25, 2021 3:40 pm Post subject: |
|
|
Why install this version with gem when you can install from official tree?
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
web.user
n00b
Joined: 14 May 2021
Posts: 17
|
| Posted: Sat Sep 25, 2021 5:13 pm Post subject: |
|
|
Oh I forgot about this, sure it has to be this:
| Code: | | sudo emerge =dev-ruby/bcrypt_pbkdf-1.0.0 |
_________________
Check out ASN lookup tool to gather IP address information. |
|
| Back to top |
|
|
|
Portage & Programming
