From: binhost@demeter.amd64.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost amd64-default-17.1] Update failed
Date: Thu, 30 Jun 2022 16:21:30 +0000 (UTC) [thread overview]
Message-ID: <20220630162130.B19FB2680D3@demeter.amd64.dev.gentoo.org> (raw)
Binhost amd64-default-17.1 update failed
* media-sound/lilypond and media-gfx/imagemagick for "music" filter support
* media-gfx/graphviz for "graphviz" filter support
* Messages for package dev-lang/rust-1.60.0:
* Rust installs a helper script for calling GDB and LLDB,
* for your convenience it is installed under /usr/bin/rust-{gdb,lldb}-1.60.0.
* Messages for package sys-fs/cryfs-0.10.3-r1:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package dev-libs/glib-2.72.1:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package sys-devel/llvm-14.0.4:
* You can find additional opt-viewer utility scripts in:
* /usr/lib/llvm/14/share/opt-viewer
* To use these scripts, you will need Python along with the following
* packages:
* dev-python/pygments (for opt-viewer)
* dev-python/pyyaml (for all of them)
* Messages for package media-libs/mesa-22.0.5:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package sys-devel/clang-14.0.4:
* You can find additional utility scripts in:
* /usr/lib/llvm/14/share/clang
* Some of them are vim integration scripts (with instructions inside).
* The run-clang-tidy.py script requires the following additional package:
* dev-python/pyyaml
* Messages for package media-libs/gegl-0.4.34:
* Install additional packages for optional runtime features:
* media-gfx/graphviz for 'Show Image Graph' under GIMP[debug] menu 'File - Debug'
* Messages for package gui-libs/gtk-4.6.4-r1:
* Please install app-text/evince for print preview functionality.
* Alternatively, check "gtk-print-preview-command" documentation and
* add it to your settings.ini file.
* Messages for package dev-qt/qtwebengine-5.15.4_p20220526:
* This version of Qt WebEngine is based on Chromium version 87.0.4280.144,
* with additional security fixes from newer versions. Extensive as it is, the
* list of backports is impossible to evaluate, but always bound to be behind
* Chromium's release schedule.
* In addition, various online services may deny service based on an outdated
* user agent version (and/or other checks). Google is already known to do so.
*
* tldr: Your web browsing experience will be compromised.
* Messages for package sys-apps/portage-3.0.30-r3:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package dev-ruby/bundler-2.1.4:
* ERROR: dev-ruby/bundler-2.1.4::gentoo failed (compile phase):
* failed to (re)build documentation
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 2174: Called ruby-ng_src_compile
* environment, line 1774: Called _ruby_invoke_environment 'all' 'all_ruby_compile'
* environment, line 614: Called all_ruby_compile
* environment, line 723: Called all_fakegem_compile
* environment, line 684: Called die
* The specific snippet of code:
* rdoc ${RUBY_FAKEGEM_DOC_SOURCES} || die "failed to (re)build documentation";
*
* If you need support, post the output of `emerge --info '=dev-ruby/bundler-2.1.4::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-ruby/bundler-2.1.4::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment'.
* Working directory: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
* S: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
* Messages for package net-misc/networkmanager-1.36.4:
* Unable to find kernel sources at /usr/src/linux
*
* 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'
*
* Regenerating GNU info directory index...
* Processed 127 info files.
!!! 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 . .\b\b... 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/json-2.0.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
*
* >=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
*
* >=dev-ruby/minitest-5.11.3[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
*
* >=dev-ruby/rake-12.3.2[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/power_assert-1.1.3[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
*
* 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-1656584221
next reply other threads:[~2022-06-30 16:21 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:21 binhost [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-17 10:18 [gentoo-binhost-autobuilds] [binhost amd64-default-17.1] Update failed binhost
2023-07-16 10:17 binhost
2023-07-15 10:18 binhost
2023-07-14 10:17 binhost
2023-07-13 10:17 binhost
2023-07-12 10:17 binhost
2023-07-11 10:17 binhost
2023-07-10 10:18 binhost
2023-07-09 10:18 binhost
2023-07-08 10:17 binhost
2023-07-07 10:20 binhost
2023-07-06 10:20 binhost
2023-07-05 10:21 binhost
2023-07-04 10:23 binhost
2023-07-03 10:23 binhost
2022-12-30 12:06 binhost
2022-12-29 10:17 binhost
2022-12-28 10:17 binhost
2022-12-27 10:17 binhost
2022-12-26 10:18 binhost
2022-12-25 10:18 binhost
2022-12-24 10:18 binhost
2022-12-23 10:18 binhost
2022-12-22 10:18 binhost
2022-12-21 10:18 binhost
2022-12-20 10:18 binhost
2022-12-19 10:18 binhost
2022-12-18 10:18 binhost
2022-12-17 10:18 binhost
2022-12-16 10:18 binhost
2022-12-15 10:18 binhost
2022-07-18 10:21 binhost
2022-07-17 10:19 binhost
2022-07-16 10:21 binhost
2022-07-15 10:24 binhost
2022-07-14 10:47 binhost
2022-07-13 10:44 binhost
2022-07-12 10:33 binhost
2022-07-11 16:41 binhost
2022-07-10 12:07 binhost
2022-07-09 10:17 binhost
2022-07-08 10:17 binhost
2022-07-07 10:17 binhost
2022-07-06 10:17 binhost
2022-07-05 10:17 binhost
2022-07-04 10:17 binhost
2022-07-03 10:17 binhost
2022-07-02 10:32 binhost
2022-07-01 12:58 binhost
2022-06-29 10:22 binhost
2022-06-28 10:18 binhost
2022-06-27 10:19 binhost
2022-06-26 10:21 binhost
2022-06-25 10:19 binhost
2022-06-24 10:19 binhost
2022-06-23 10:19 binhost
2022-06-22 12:52 binhost
2022-06-21 10:18 binhost
2022-06-20 10:20 binhost
2022-06-19 10:44 binhost
2022-06-18 10:19 binhost
2022-06-17 10:21 binhost
2022-06-16 10:18 binhost
2022-06-15 11:08 binhost
2022-06-14 10:21 binhost
2022-06-13 10:19 binhost
2022-06-12 10:34 binhost
2022-06-11 10:19 binhost
2022-06-10 13:22 binhost
2022-06-09 10:21 binhost
2022-06-08 10:41 binhost
2022-06-07 10:19 binhost
2022-06-06 10:20 binhost
2022-06-05 11:05 binhost
2022-06-04 10:22 binhost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220630162130.B19FB2680D3@demeter.amd64.dev.gentoo.org \
--to=binhost@demeter.amd64.dev.gentoo.org \
--cc=gentoo-binhost-autobuilds@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox