* [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
@ 2024-08-02 3:30 binhost
0 siblings, 0 replies; 5+ messages in thread
From: binhost @ 2024-08-02 3:30 UTC (permalink / raw
To: gentoo-binhost-autobuilds
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Fri Aug 2 03:30:11 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
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-kde-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-kde-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Machine binhost-arm64-gnome-23
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-gnome-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-gnome-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Machine binhost-arm64-server-23
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-server-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-server-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Upsyncing binpackages from /var/lib/machines/binhost-arm64-kde-23/var/cache/binpkgs to arm64/23.0/arm64
rsync: [sender] change_dir "/var/lib/machines/binhost-arm64-kde-23/var/cache/binpkgs" failed: No such file or directory (2)
Number of files: 0
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 0 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 0
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 51
Total bytes received: 15
sent 51 bytes received 15 bytes 18.86 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.3.0]
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722569410
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
@ 2024-08-03 3:32 binhost
0 siblings, 0 replies; 5+ messages in thread
From: binhost @ 2024-08-03 3:32 UTC (permalink / raw
To: gentoo-binhost-autobuilds
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
@ 2024-08-04 3:33 binhost
0 siblings, 0 replies; 5+ messages in thread
From: binhost @ 2024-08-04 3:33 UTC (permalink / raw
To: gentoo-binhost-autobuilds
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Sun Aug 4 03:30:20 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 19025 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.
* 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
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 7) dev-python/ensurepip-setuptools-71.0.4::gentoo
>>> Emerging (2 of 7) dev-util/astyle-3.4.9::gentoo
>>> Emerging (3 of 7) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-python/ensurepip-setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
>>> Failed to emerge dev-util/astyle-3.4.9, Log file:
>>> '/var/tmp/portage/dev-util/astyle-3.4.9/temp/build.log'
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 4) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 3) dev-lang/python-3.11.9_p1::gentoo
>>> Emerging (2 of 3) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-lang/python-3.11.9_p1, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/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'
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 7 packages have failed to build, install, or execute
* postinst:
*
* (dev-python/ensurepip-setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
* (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-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-lang/python-3.11.9_p1:3.11/3.11::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/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.
* IMPORTANT: 22 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 6) dev-python/ensurepip-setuptools-71.0.4::gentoo
>>> Emerging (2 of 6) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-python/ensurepip-setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 4) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 3) dev-lang/python-3.11.9_p1::gentoo
>>> Emerging (2 of 3) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-lang/python-3.11.9_p1, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 1) games-board/gnome-mahjongg-3.40.1::gentoo
>>> Failed to emerge games-board/gnome-mahjongg-3.40.1, Log file:
>>> '/var/tmp/portage/games-board/gnome-mahjongg-3.40.1/temp/build.log'
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package games-board/gnome-mahjongg-3.40.1:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 6 packages have failed to build, install, or execute
* postinst:
*
* (dev-python/ensurepip-setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
* (dev-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-lang/python-3.11.9_p1:3.11/3.11::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
* (games-board/gnome-mahjongg-3.40.1:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/games-board/gnome-mahjongg-3.40.1/temp/build.log'
*
Container binhost-arm64-gnome-23 failed with error code 1.
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.
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Emerging (1 of 3) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 2) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 1) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 3 packages have failed to build, install, or execute
* postinst:
*
* (dev-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
*
Container binhost-arm64-server-23 failed with error code 1.
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: 3 (reg: 2, dir: 1)
Number of regular files transferred: 2
Total file size: 9,185,383,986 bytes
Total transferred file size: 5,418,546 bytes
Literal data: 335,748 bytes
Matched data: 5,082,798 bytes
File list size: 131,055
File list generation time: 0.147 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 513,753
Total bytes received: 17,653
sent 513,753 bytes received 17,653 bytes 96,619.27 bytes/sec
total size is 9,185,383,986 speedup is 17,285.06
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722742220
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
@ 2024-08-05 3:34 binhost
0 siblings, 0 replies; 5+ messages in thread
From: binhost @ 2024-08-05 3:34 UTC (permalink / raw
To: gentoo-binhost-autobuilds
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Mon Aug 5 03:30:05 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 19022 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.
* 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
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 9) dev-python/ensurepip-setuptools-71.0.4::gentoo
>>> Emerging (2 of 9) dev-util/astyle-3.4.9::gentoo
>>> Failed to emerge dev-python/ensurepip-setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
>>> 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...
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 7) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 6) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 5) dev-lang/python-3.11.9_p1::gentoo
>>> Emerging (2 of 5) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-lang/python-3.11.9_p1, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 3) media-libs/raptor-2.0.16::gentoo
>>> Emerging (2 of 3) media-fonts/noto-20240630::gentoo
>>> Failed to emerge media-libs/raptor-2.0.16, Log file:
>>> '/var/tmp/portage/media-libs/raptor-2.0.16/temp/build.log'
>>> Failed to emerge media-fonts/noto-20240630, Log file:
>>> '/var/tmp/portage/media-fonts/noto-20240630/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'
* Messages for package dev-lang/python-3.12.4_p3:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/setuptools-71.0.4:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package media-fonts/noto-20240630:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 9 packages have failed to build, install, or execute
* postinst:
*
* (dev-python/ensurepip-setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
* (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-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-lang/python-3.11.9_p1:3.11/3.11::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
* (media-libs/raptor-2.0.16:2/2::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/media-libs/raptor-2.0.16/temp/build.log'
* (media-fonts/noto-20240630:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/media-fonts/noto-20240630/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.
* IMPORTANT: 22 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 7) dev-python/ensurepip-setuptools-71.0.4::gentoo
>>> Failed to emerge dev-python/ensurepip-setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 6) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 5) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Running pre-merge checks for dev-lang/python-3.11.9_p1
>>> Emerging (1 of 4) dev-lang/python-3.11.9_p1::gentoo
>>> Failed to emerge dev-lang/python-3.11.9_p1, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 3) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 2) media-libs/raptor-2.0.16::gentoo
>>> Failed to emerge media-libs/raptor-2.0.16, Log file:
>>> '/var/tmp/portage/media-libs/raptor-2.0.16/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 1) games-board/gnome-mahjongg-3.40.1::gentoo
>>> Failed to emerge games-board/gnome-mahjongg-3.40.1, Log file:
>>> '/var/tmp/portage/games-board/gnome-mahjongg-3.40.1/temp/build.log'
* Messages for package dev-lang/python-3.12.4_p3:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/setuptools-71.0.4:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package games-board/gnome-mahjongg-3.40.1:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 7 packages have failed to build, install, or execute
* postinst:
*
* (dev-python/ensurepip-setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/ensurepip-setuptools-71.0.4/temp/build.log'
* (dev-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-lang/python-3.11.9_p1:3.11/3.11::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.11.9_p1/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
* (media-libs/raptor-2.0.16:2/2::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/media-libs/raptor-2.0.16/temp/build.log'
* (games-board/gnome-mahjongg-3.40.1:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/games-board/gnome-mahjongg-3.40.1/temp/build.log'
*
Container binhost-arm64-gnome-23 failed with error code 1.
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.
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-lang/python-3.12.4_p3
>>> Emerging (1 of 3) dev-lang/python-3.12.4_p3::gentoo
>>> Failed to emerge dev-lang/python-3.12.4_p3, Log file:
>>> '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 2) dev-python/jaraco-text-3.14.0::gentoo
>>> Failed to emerge dev-python/jaraco-text-3.14.0, Log file:
>>> '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
*** Resuming merge...
>>> Emerging (1 of 1) dev-python/setuptools-71.0.4::gentoo
>>> Failed to emerge dev-python/setuptools-71.0.4, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
* Messages for package dev-lang/python-3.12.4_p3:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/jaraco-text-3.14.0:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package dev-python/setuptools-71.0.4:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 3 packages have failed to build, install, or execute
* postinst:
*
* (dev-lang/python-3.12.4_p3:3.12/3.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-lang/python-3.12.4_p3/temp/build.log'
* (dev-python/jaraco-text-3.14.0:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/jaraco-text-3.14.0/temp/build.log'
* (dev-python/setuptools-71.0.4:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/dev-python/setuptools-71.0.4/temp/build.log'
*
Container binhost-arm64-server-23 failed with error code 1.
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: 10 (reg: 10)
Number of deleted files: 11 (reg: 10, dir: 1)
Number of regular files transferred: 12
Total file size: 9,185,383,986 bytes
Total transferred file size: 53,935,666 bytes
Literal data: 49,001,555 bytes
Matched data: 4,934,111 bytes
File list size: 131,055
File list generation time: 0.133 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 49,191,142
Total bytes received: 17,871
sent 49,191,142 bytes received 17,871 bytes 3,936,721.04 bytes/sec
total size is 9,185,383,986 speedup is 186.66
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722828605
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
@ 2024-08-06 7:24 binhost
0 siblings, 0 replies; 5+ messages in thread
From: binhost @ 2024-08-06 7:24 UTC (permalink / raw
To: gentoo-binhost-autobuilds
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Tue Aug 6 07:23:14 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] "crossdev" /var/db/repos/crossdev (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...EMPTY!
[2] "local" /var/db/repos/local (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...Finished
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19022 packages in 170 categories
* 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.
* IMPORTANT: 23 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: 1423
Packages in world: 21
Packages in system: 49
Required packages: 1423
Number removed: 0
>>> Building file list for packages cleaning...
>>> Your packages directory was already clean.
Container binhost-arm64-kde-23 exited successfully.
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.
* IMPORTANT: 22 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Container binhost-arm64-gnome-23 terminated by signal KILL.
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.
* 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,891 (reg: 3,280, dir: 1,611)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 9,303,559,971 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 131,067
File list generation time: 0.040 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 168,102
Total bytes received: 15
sent 168,102 bytes received 15 bytes 48,033.43 bytes/sec
total size is 9,303,559,971 speedup is 55,339.79
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722928994
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-08-06 7:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-04 3:33 [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed binhost
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 7:24 binhost
2024-08-05 3:34 binhost
2024-08-03 3:32 binhost
2024-08-02 3:30 binhost
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox