From: binhost@jiji.arm.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
Date: Sat, 03 Aug 2024 03:32:57 +0000 [thread overview]
Message-ID: <9a262ccd48bee431e8e23cfdeb696ec3@susuwatari.arm.dev.gentoo.org> (raw)
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Sat Aug 3 03:30:16 AM UTC 2024
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 170 categories of packages...Finished
[1] "" /var/db/repos/crossdev (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...EMPTY!
[2] "" /var/db/repos/local (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...EMPTY!
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19023 packages in 170 categories
!!! Section 'local' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/local'
!!! Section 'crossdev' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/crossdev'
* IMPORTANT: 8 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Machine binhost-arm64-kde-23
HEAD is now at 36487a8 Fix useflags for mate
Spawning container binhost-arm64-kde-23 on /var/lib/machines/binhost-arm64-kde-23.
Press Ctrl-] three times within 1s to kill container.
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
* IMPORTANT: 23 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
The following packages are causing rebuilds:
(dev-util/astyle-3.4.9:0/3.2::gentoo, ebuild scheduled for merge) causes rebuilds for:
(dev-util/kdevelop-24.05.2:5/24.05::gentoo, ebuild scheduled for merge)
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) dev-util/astyle-3.4.9::gentoo
>>> Failed to emerge dev-util/astyle-3.4.9, Log file:
>>> '/var/tmp/portage/dev-util/astyle-3.4.9/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 1) dev-util/kdevelop-24.05.2::gentoo
>>> Failed to emerge dev-util/kdevelop-24.05.2, Log file:
>>> '/var/tmp/portage/dev-util/kdevelop-24.05.2/temp/build.log'
*
* The following 2 packages have failed to build, install, or execute
* postinst:
*
* (dev-util/astyle-3.4.9:0/3.2::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-util/astyle-3.4.9/temp/build.log'
* (dev-util/kdevelop-24.05.2:5/24.05::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-util/kdevelop-24.05.2/temp/build.log'
*
Container binhost-arm64-kde-23 failed with error code 1.
Machine binhost-arm64-gnome-23
HEAD is now at 36487a8 Fix useflags for mate
Spawning container binhost-arm64-gnome-23 on /var/lib/machines/binhost-arm64-gnome-23.
Press Ctrl-] three times within 1s to kill container.
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
* IMPORTANT: 22 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: 1122
Packages in world: 19
Packages in system: 49
Required packages: 1122
Number removed: 0
>>> Building file list for packages cleaning...
>>> Your packages directory was already clean.
Container binhost-arm64-gnome-23 exited successfully.
Machine binhost-arm64-server-23
HEAD is now at 36487a8 Fix useflags for mate
Spawning container binhost-arm64-server-23 on /var/lib/machines/binhost-arm64-server-23.
Press Ctrl-] three times within 1s to kill container.
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
* IMPORTANT: 18 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: 331
Packages in world: 9
Packages in system: 49
Required packages: 331
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-23/var/cache/binpkgs to arm64/23.0/arm64
Number of files: 4,887 (reg: 3,278, dir: 1,609)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 9,185,383,986 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 131,055
File list generation time: 0.064 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 167,971
Total bytes received: 15
sent 167,971 bytes received 15 bytes 47,996.00 bytes/sec
total size is 9,185,383,986 speedup is 54,679.46
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722655816
next reply other threads:[~2024-08-03 3:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 3:32 binhost [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 7:24 [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed binhost
2024-08-05 3:34 binhost
2024-08-04 3:33 binhost
2024-08-02 3:30 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=9a262ccd48bee431e8e23cfdeb696ec3@susuwatari.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