>>> Test phase: dev-ruby/ffi-1.14.2 * Running test phase for ruby26 ... /usr/lib/ruby/site_ruby/2.6.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'rspec-support' (~> 3.10.0) - did find: [rspec-support-3.9.4] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/var/tmp/portage/dev-ruby/ffi-1.14.2/homedir/.gem/ruby/2.6.0:/usr/lib/ruby/gems/2.6.0:/usr/local/lib/ruby/gems/2.6.0', execute `gem env` for more information from /usr/lib/ruby/site_ruby/2.6.0/rubygems/specification.rb:1446:in `block in activate_dependencies' from /usr/lib/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `each' from /usr/lib/ruby/site_ruby/2.6.0/rubygems/specification.rb:1435:in `activate_dependencies' from /usr/lib/ruby/site_ruby/2.6.0/rubygems/specification.rb:1417:in `activate' from /usr/lib/ruby/site_ruby/2.6.0/rubygems.rb:224:in `rescue in try_activate' from /usr/lib/ruby/site_ruby/2.6.0/rubygems.rb:217:in `try_activate' from /usr/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:123:in `rescue in require' from /usr/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require' from /usr/lib/ruby/gems/2.6.0/gems/rspec-core-3.10.1/bin/rspec:3:in `<top (required)>' from /usr/bin/rspec:9:in `load' from /usr/bin/rspec:9:in `<main>' /usr/lib/ruby/site_ruby/2.6.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'rspec-support' (~> 3.10.0) - did find: [rspec-support-3.9.4] (Gem::MissingSpecVersionError)
It's not clear to me how this could happen. Perhaps a weirdly broken rspec install? Although in that case I would expect rspec to still be 3.9 and rspec-support to be 3.10 and it looks like things are the other way around.
Portage does not block this: chroot ~ # equery l dev-ruby/rspec-support dev-ruby/rspec * Searching for rspec-support in dev-ruby ... [IP-] [ ] dev-ruby/rspec-support-3.10.2:3 * Searching for rspec in dev-ruby ... [IP-] [ ] dev-ruby/rspec-3.10.0:3 chroot ~ # emerge -p1vt =dev-ruby/rspec-support-3.9.4 These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild UD ] dev-ruby/rspec-support-3.9.4:3::gentoo [3.10.2:3::gentoo] USE="-doc -test" RUBY_TARGETS="ruby26 (-ruby25) (-ruby27) (-ruby30%)" 0 KiB Total: 1 package (1 downgrade), Size of downloads: 0 KiB IIRC it was automatically downgraded by something else, at least I did not do it by hand. ffi does not specify any requirements on them.
(In reply to Rolf Eike Beer from comment #2) > Portage does not block this: > > chroot ~ # equery l dev-ruby/rspec-support dev-ruby/rspec > * Searching for rspec-support in dev-ruby ... > [IP-] [ ] dev-ruby/rspec-support-3.10.2:3 > > * Searching for rspec in dev-ruby ... > [IP-] [ ] dev-ruby/rspec-3.10.0:3 > chroot ~ # emerge -p1vt =dev-ruby/rspec-support-3.9.4 > > These are the packages that would be merged, in reverse order: > > Calculating dependencies... done! > [ebuild UD ] dev-ruby/rspec-support-3.9.4:3::gentoo [3.10.2:3::gentoo] > USE="-doc -test" RUBY_TARGETS="ruby26 (-ruby25) (-ruby27) (-ruby30%)" 0 KiB > > Total: 1 package (1 downgrade), Size of downloads: 0 KiB That is strange because all the rspec components depend on the matching versions, e.g. rspec-core-3.10.1 depends on =rspec-support-3.10* (and rspec itself depends on the components in the same way. > IIRC it was automatically downgraded by something else, at least I did not > do it by hand. Nothing else depends on rspec-support other than the three rspec components so I'm not sure how that would happen. There are also no packages that specifically require rspec 3.9. > ffi does not specify any requirements on them. These are set in the eclass, but they should require rspec:3, and that matches the ffi dependencies.
