[gentoo-binhost-autobuilds] [binhost amd64-default-17.1] Update failed

Binhost amd64-default-17.1 update failed


Spawning container binhost-amd64-x86-64 on /var/lib/machines/binhost-amd64-x86-64.
Press ^] three times within 1s to kill container.

 * IMPORTANT: 19 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

Calculating dependencies  
 * IMPORTANT: 19 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

. 

!!! Problem resolving dependencies for sci-electronics/klayout from @selected
... done!

!!! The ebuild selected to satisfy "sci-electronics/klayout" has unmet requirements.
- sci-electronics/klayout-0.27.3::gentoo USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python3_8 -python3_9" RUBY_TARGETS="ruby27"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_python3_8 python_single_target_python3_9 )

  The above constraints are a subset of the following complete expression:
    exactly-one-of ( python_single_target_python3_8 python_single_target_python3_9 ) any-of ( ruby_targets_ruby27 )

(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies  . .... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   >=dev-ruby/test-unit-3.2.9[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/minitest-5.11.3[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   dev-libs/libffi:0/7= pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/net-telnet-0.2.0[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/did_you_mean-1.2.1[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/rake-12.3.2[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/power_assert-1.1.3[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/json-2.0.2[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   virtual/rubygems[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   virtual/rubygems[ruby_targets_ruby26(-)] pulled in by:
 *     dev-ruby/bundler-2.1.4
 * 
 *   >=dev-ruby/rdoc-6.1.2[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 * 
 *   emerge --update --newuse --deep --with-bdeps=y @world
 * 
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 * 
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the repository, since it may not
 * be possible to satisfy their dependencies.
Container binhost-amd64-x86-64 failed with error code 1.



Full build log at /root/.tmp-binhost-amd64-default-17.1-update-1657275421