Created attachment 848601 [details] dev-ruby:rspec-expectations-3.11.1:20230115-183640.log =dev-ruby/rspec-expectations-3.11.1 fails its test phase with the following error and stack-trace: Traceback (most recent call last): 8: from /usr/bin/rspec-3:8:in `<main>' 7: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem' 6: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' 5: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 4: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/specification.rb:1371:in `activate' 3: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/specification.rb:1389:in `activate_dependencies' 2: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/specification.rb:1389:in `each' 1: from /usr/lib64/ruby/site_ruby/2.7.0/rubygems/specification.rb:1400:in `block in activate_dependencies' /usr/lib64/ruby/site_ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'rspec-core' (~> 3.10.0) - did find: [rspec-core-3.11.0,rspec-core-2.99.2] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/var/tmp/portage/dev-ruby/rspec-expectations-3.11.1/homedir/.gem/ruby/2.7.0:/usr/lib64/ruby/gems/2.7.0:/usr/local/lib64/ruby/gems/2.7.0', execute `gem env` for more information I guess that wherever the dependency on rspec-core is declared, it's specified as being the exact (major-minor) version 3.10.0 instead of being either an "or-later" version or the same major-minor version as this version of rspec-expectations (3.11.1). Or possibly this is coming via rspec-mocks, which was set to be upgraded to 3.11.2 after this was built, in which case perhaps this should depend on >=rspec-mocks-${SUBVERSION}?
Created attachment 848603 [details] emerge-info.txt
