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

Binhost amd64-default-17.1 update failed


 * Install additional packages for optional runtime features:
 *   x11-misc/colord for color management support
 * 
 * In Plasma 5.20, default behavior of the Task Switcher to move minimised
 * windows to the end of the list was changed so that it remains in the
 * original order. To revert to the well established behavior:
 * 
 *  - Edit ~/.config/kwinrc
 *  - Find [TabBox] section
 *  - Add "MoveMinimizedWindowsToEndOfTabBoxFocusChain=true"
 * Messages for package kde-plasma/kinfocenter-5.24.5:
 * Install additional packages for optional runtime features:
 *   app-misc/wayland-utils for Wayland information module
 *   x11-apps/mesa-progs for OpenGL information module
 *   x11-apps/xdpyinfo for X Server information module
 * Messages for package kde-plasma/kde-gtk-config-5.24.5:
 * If you notice missing icons in your GTK applications, you may have to install
 * the corresponding themes for GTK. A good guess would be x11-themes/oxygen-gtk
 * for example.
 * Messages for package kde-plasma/plasma-workspace-5.24.5-r1:
 * To enable gpg-agent and/or ssh-agent in Plasma sessions,
 * edit /etc/xdg/plasma-workspace/env/10-agent-startup.sh
 * and /etc/xdg/plasma-workspace/shutdown/10-agent-shutdown.sh
 * Messages for package kde-apps/akonadi-21.12.3:
 * 
 * Attention: Make sure to read README.gentoo after install.
 * 
 * You can select the storage backend in ~/.config/akonadi/akonadiserverrc.
 * Available drivers are:
 *   QMYSQL
 * QMYSQL has been set as your default akonadi storage backend.
 * 
 * Akonadi QMYSQL backends that were created using <dev-db/mariadb-10.5.9-r3 may
 * be in need of a manual fix. Failure to do so could result in akonadi service
 * to stop fetching and sending mail for KMail or any other kind of issues in PIM
 * applications depending on akonadi like KOrganizer, KAddressBook etc.
 * 
 * Note:
 * - All commands that follow are to be run by a regular user.
 * - They will have to be repeated for any other user of KDE PIM.
 * - Use your favorite terminal.
 * 
 * 1) Check if "mysql" system db is present:
 * $ mysql -S /run/user/$(id -u)/akonadi/mysql.socket -e 'select schema_name \
 * from information_schema.schemata where schema_name = "mysql"'
 * 
 * The output obtained should look like this:
 * +-------------+
 * | schema_name |
 * +-------------+
 * | mysql       |
 * +-------------+
 * 
 * If so, then automatic DB upgrades will succeed, no further action necessary.
 * 
 * 2) If, however, the above query returned empty, add the missing database:
 * $ mysql -S /run/user/$(id -u)/akonadi/mysql.socket -e 'create database mysql'
 * 
 * Future MariaDB releases should upgrade without manual intervention now.
 * 
 * 3) Optional: You may have come here with an already defunct akonadi service.
 * To manually fix the akonadi MariaDB backend:
 * $ mysql_upgrade --defaults-file=~/.local/share/akonadi/mysql.conf \
 * -S /run/user/$(id -u)/akonadi/mysql.socket
 * 
 * Don't forget to restart the akonadi service afterwards:
 * $ akonadictl restart
 * 
 * References:
 * [1] https://bugs.gentoo.org/688746
 * [2] https://bugs.kde.org/show_bug.cgi?id=409224
 * 
 * (Note: Above message is only printed the first time package is
 * installed. Please look at /usr/share/doc/akonadi-21.12.3/README.gentoo*
 * for future reference)






































 * 
 * The following package has failed to build, install, or execute postinst:
 * 
 *  (dev-ruby/bundler-2.1.4:2/2::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'
 * 

 * GNU info directory index is up-to-date.

!!! existing preserved libs:
>>> package: dev-libs/libffi-3.4.2-r1
 *  - /usr/lib64/libffi.so.7
 *  - /usr/lib64/libffi.so.7.1.0
 *      used by /usr/lib64/ruby/2.6.0/x86_64-linux/fiddle.so (dev-lang/ruby-2.6.10)
Use emerge @preserved-rebuild to rebuild packages using these libraries

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

 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

 * 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:
 * 
 *   virtual/rubygems[ruby_targets_ruby26(-)] pulled in by:
 *     dev-ruby/bundler-2.1.4
 * 
 *   >=dev-ruby/xmlrpc-0.3.0[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/json-2.0.2[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-ruby/power_assert-1.1.3[ruby_targets_ruby26] pulled in by:
 *     dev-lang/ruby-2.6.10
 * 
 *   >=dev-ruby/test-unit-3.2.9[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/rdoc-6.1.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
 * 
 *   >=dev-ruby/net-telnet-0.2.0[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
 * 
 * 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-1655893021