From: binhost@jiji.arm.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost arm64/xx.x/arm64] Update possibly failed
Date: Sun, 31 Dec 2023 11:55:39 +0000 [thread overview]
Message-ID: <c378ff6183140a07ddcf3fc076c425d5@jiji.arm.dev.gentoo.org> (raw)
Binhost arm64/xx.x/arm64 update produced long output
Starting run at Sun Dec 31 11:51:19 AM UTC 2023
Syncing host
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /var/db/repos/gentoo/ (cache: metadata-md5-or-flat)
Reading up to 167 categories of packages...Finished
[1] "crossdev" /var/db/repos/crossdev (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 167 categories of packages...EMPTY!
[2] "local" /var/db/repos/local (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 167 categories of packages...Finished
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19028 packages in 167 categories
Machine binhost-arm64-kde
Spawning container binhost-arm64-kde on /var/lib/machines/binhost-arm64-kde.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 16 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* 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!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed: 1391
Packages in world: 21
Packages in system: 49
Required packages: 1391
Number removed: 0
>>> Building file list for packages cleaning...
>>> Your packages directory was already clean.
Container binhost-arm64-kde exited successfully.
Machine binhost-arm64-gnome
Spawning container binhost-arm64-gnome on /var/lib/machines/binhost-arm64-gnome.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 15 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* 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!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed: 1105
Packages in world: 18
Packages in system: 49
Required packages: 1105
Number removed: 0
/root/bin/run-update: line 10: eclean-pkg: command not found
Container binhost-arm64-gnome failed with error code 127.
Machine binhost-arm64-server
Spawning container binhost-arm64-server on /var/lib/machines/binhost-arm64-server.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 14 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* 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!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed: 334
Packages in world: 9
Packages in system: 49
Required packages: 334
Number removed: 0
>>> Building file list for packages cleaning...
>>> Your packages directory was already clean.
Container binhost-arm64-server exited successfully.
Machine binhost-arm64-kde-23
Spawning container binhost-arm64-kde-23 on /var/lib/machines/binhost-arm64-kde-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 16 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
The following packages are causing rebuilds:
(kde-frameworks/kio-5.113.0-r1:5/5.113::gentoo, ebuild scheduled for merge) causes rebuilds for:
(kde-apps/dolphin-23.08.3:5/5::gentoo, ebuild scheduled for merge)
(kde-frameworks/kwindowsystem-5.113.0:5/5.113::gentoo, ebuild scheduled for merge) causes rebuilds for:
(kde-plasma/kwayland-integration-5.27.10:5/5::gentoo, ebuild scheduled for merge)
(kde-plasma/kwin-5.27.10-r1:5/5::gentoo, ebuild scheduled for merge)
(kde-frameworks/kglobalaccel-5.113.0:5/5.113::gentoo, ebuild scheduled for merge) causes rebuilds for:
(kde-plasma/kwin-5.27.10-r1:5/5::gentoo, ebuild scheduled for merge)
(kde-frameworks/kidletime-5.113.0:5/5.113::gentoo, ebuild scheduled for merge) causes rebuilds for:
(kde-plasma/kwin-5.27.10-r1:5/5::gentoo, ebuild scheduled for merge)
>>> Verifying ebuild manifests
>>> Running pre-merge checks for kde-frameworks/kirigami-5.113.0
^[[31;01m*^[[0m Your current compiler does not support OpenMP!
^[[31;01m*^[[0m Enable OpenMP support by building sys-devel/gcc with USE="openmp".
^[[31;01m*^[[0m ERROR: kde-frameworks/kirigami-5.113.0::gentoo failed (pretend phase):
^[[31;01m*^[[0m Active compiler does not have required support for OpenMP
^[[31;01m*^[[0m
^[[31;01m*^[[0m Call stack:
^[[31;01m*^[[0m ebuild.sh, line 136: Called pkg_pretend
^[[31;01m*^[[0m kirigami-5.113.0.ebuild, line 38: Called tc-check-openmp
^[[31;01m*^[[0m toolchain-funcs.eclass, line 602: Called die
^[[31;01m*^[[0m The specific snippet of code:
^[[31;01m*^[[0m die "Active compiler does not have required support for OpenMP"
^[[31;01m*^[[0m
^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=kde-frameworks/kirigami-5.113.0::gentoo'`,
^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=kde-frameworks/kirigami-5.113.0::gentoo'`.
^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/build.log'.
^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/die.env'.
^[[31;01m*^[[0m Working directory: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/empty'
^[[31;01m*^[[0m S: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/work/kirigami2-5.113.0'
>>> Failed to emerge kde-frameworks/kirigami-5.113.0, Log file:
>>> '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/build.log'
>>> Running pre-merge checks for sys-apps/portage-3.0.59
^[[32m*^[[0m Checking for suitable kernel configuration options ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
>>> Running pre-merge checks for app-office/libreoffice-7.5.6.2
^[[33;01m*^[[0m If you plan to use Base application you must enable USE base.
^[[33;01m*^[[0m Without USE java, several wizards are not going to be available.
^[[32m*^[[0m Checking for at least 512 MiB RAM ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 6 GiB disk space at "/var/tmp/portage/app-office/libreoffice-7.5.6.2/temp" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
*** Resuming merge...
^[[32m * ^[[39;49;00mPackage: kde-frameworks/kirigami-5.113.0:5/5.113
^[[32m * ^[[39;49;00mRepository: gentoo
^[[32m * ^[[39;49;00mMaintainer: kde@gentoo.org
^[[32m * ^[[39;49;00mUpstream: https://bugs.kde.org/
^[[32m * ^[[39;49;00mUSE: arm64 elibc_glibc kernel_linux openmp
^[[32m * ^[[39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox
^[[31;01m*^[[0m Your current compiler does not support OpenMP!
^[[31;01m*^[[0m Enable OpenMP support by building sys-devel/gcc with USE="openmp".
^[[31;01m*^[[0m ERROR: kde-frameworks/kirigami-5.113.0::gentoo failed (pretend phase):
^[[31;01m*^[[0m Active compiler does not have required support for OpenMP
^[[31;01m*^[[0m
^[[31;01m*^[[0m Call stack:
^[[31;01m*^[[0m ebuild.sh, line 136: Called pkg_pretend
^[[31;01m*^[[0m kirigami-5.113.0.ebuild, line 38: Called tc-check-openmp
^[[31;01m*^[[0m toolchain-funcs.eclass, line 602: Called die
^[[31;01m*^[[0m The specific snippet of code:
^[[31;01m*^[[0m die "Active compiler does not have required support for OpenMP"
^[[31;01m*^[[0m
^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=kde-frameworks/kirigami-5.113.0::gentoo'`,
^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=kde-frameworks/kirigami-5.113.0::gentoo'`.
^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/build.log'.
^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/die.env'.
^[[31;01m*^[[0m Working directory: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/empty'
^[[31;01m*^[[0m S: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/work/kirigami2-5.113.0'
* Messages for package kde-frameworks/kirigami-5.113.0:
* Your current compiler does not support OpenMP!
* Enable OpenMP support by building sys-devel/gcc with USE="openmp".
* ERROR: kde-frameworks/kirigami-5.113.0::gentoo failed (pretend phase):
* Active compiler does not have required support for OpenMP
*
* Call stack:
* ebuild.sh, line 136: Called pkg_pretend
* kirigami-5.113.0.ebuild, line 38: Called tc-check-openmp
* toolchain-funcs.eclass, line 602: Called die
* The specific snippet of code:
* die "Active compiler does not have required support for OpenMP"
*
* If you need support, post the output of `emerge --info '=kde-frameworks/kirigami-5.113.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=kde-frameworks/kirigami-5.113.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/die.env'.
* Working directory: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/empty'
* S: '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/work/kirigami2-5.113.0'
* Messages for package app-office/libreoffice-7.5.6.2:
* If you plan to use Base application you must enable USE base.
* Without USE java, several wizards are not going to be available.
* One or more packages are either masked or have missing dependencies:
*
* =kde-frameworks/kconfig-5.112*:5 pulled in by:
* (kde-frameworks/purpose-5.112.0-r1:5/5.112::gentoo, installed)
*
* =kde-frameworks/attica-5.112*:5 pulled in by:
* (kde-frameworks/knewstuff-5.112.0:5/5.112::gentoo, installed)
*
* =kde-frameworks/kconfig-5.112*:5 pulled in by:
* (kde-frameworks/krunner-5.112.0-r1:5/5.112::gentoo, installed)
*
* =kde-frameworks/karchive-5.112*:5 pulled in by:
* (kde-plasma/libplasma-5.112.0-1:5/5.112::gentoo, installed)
*
* =kde-frameworks/kconfig-5.112*:5 pulled in by:
* (kde-frameworks/qqc2-desktop-style-5.112.0:5/5.112::gentoo, installed)
*
* =kde-frameworks/kconfig-5.112*:5 pulled in by:
* (kde-frameworks/frameworkintegration-5.112.0:5/5.112::gentoo, installed)
*
* The resume list contains packages that are either masked or have
* unsatisfied dependencies. Please restart/continue the operation
* manually, or use --skipfirst to skip the first package in the list and
* any other packages that may be masked or have missing dependencies.
*
* The following package has failed to build, install, or execute postinst:
*
* (kde-frameworks/kirigami-5.113.0:5/5.113::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/kde-frameworks/kirigami-5.113.0/temp/build.log'
*
Container binhost-arm64-kde-23 failed with error code 1.
Machine binhost-arm64-gnome-23
Spawning container binhost-arm64-gnome-23 on /var/lib/machines/binhost-arm64-gnome-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 15 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* 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!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed: 1108
Packages in world: 18
Packages in system: 49
Required packages: 1108
Number removed: 0
/root/bin/run-update: line 10: eclean-pkg: command not found
Container binhost-arm64-gnome-23 failed with error code 127.
Machine binhost-arm64-server-23
Spawning container binhost-arm64-server-23 on /var/lib/machines/binhost-arm64-server-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 14 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* 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!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed: 337
Packages in world: 9
Packages in system: 49
Required packages: 337
Number removed: 0
>>> Building file list for packages cleaning...
>>> Your packages directory was already clean.
Container binhost-arm64-server-23 exited successfully.
Upsyncing binpackages from /var/lib/machines/binhost-arm64-kde/var/cache/binpkgs to arm64/17.0/arm64
Upsyncing binpackages from /var/lib/machines/binhost-arm64-kde-23/var/cache/binpkgs to arm64/23.0/arm64
Full build log at /root/.tmp-binhost-arm64_xx.x_arm64-update-1704023479
next reply other threads:[~2023-12-31 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 11:55 binhost [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-10 5:59 [gentoo-binhost-autobuilds] [binhost arm64/xx.x/arm64] Update possibly failed binhost
2024-01-09 10:27 binhost
2024-01-08 7:55 binhost
2024-01-07 5:02 binhost
2024-01-06 10:09 binhost
2024-01-05 3:41 binhost
2024-01-04 4:30 binhost
2024-01-03 4:16 binhost
2024-01-02 4:46 binhost
2024-01-01 3:34 binhost
2023-12-31 3:44 binhost
2023-12-30 6:17 binhost
2023-12-29 6:49 binhost
2023-12-28 22:54 binhost
2023-12-28 15:46 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=c378ff6183140a07ddcf3fc076c425d5@jiji.arm.dev.gentoo.org \
--to=binhost@jiji.arm.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