From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AFF71159C9B for ; Mon, 5 Aug 2024 03:34:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8740FE2AF6; Mon, 5 Aug 2024 03:34:16 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 31D57E2AF6 for ; Mon, 5 Aug 2024 03:34:14 +0000 (UTC) Received: from susuwatari.arm.dev.gentoo.org (susuwatari.arm.dev.gentoo.org [IPv6:2a01:4f9:3051:50e1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id B3D3B33BE4D for ; Mon, 5 Aug 2024 03:34:13 +0000 (UTC) Date: Mon, 05 Aug 2024 03:34:12 +0000 Message-ID: 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 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: __DESCRIPTION__ X-BeenThere: gentoo-binhost-autobuilds@gentoo.org X-BeenThere: gentoo-binhost-autobuilds@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 4447668c-99ea-4a4c-9104-3db58efdd153 X-Archives-Hash: 9c77f09828c33c58733f9e29e5d23844 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