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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id BC1D7138330 for ; Wed, 10 Jan 2018 10:20:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE2BDE080E; Wed, 10 Jan 2018 10:20:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 99006E080E for ; Wed, 10 Jan 2018 10:20:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 461FA335C37; Wed, 10 Jan 2018 10:20:33 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: 1.175 X-Spam-Level: * X-Spam-Status: No, score=1.175 tagged_above=-9999 required=5.5 tests=[AWL=-0.255, BAYES_05=-0.5, PP_MIME_FAKE_ASCII_TEXT=0.358, RDNS_NONE=0.793, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a62H3Yy7riQE; Wed, 10 Jan 2018 10:20:23 +0000 (UTC) Received: from nightheron.gentoo.org (unknown [IPv6:2001:470:1f13:1279:21e:4fff:fe17:d5a1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id F28CF335C3B; Wed, 10 Jan 2018 10:20:22 +0000 (UTC) Received: from lgentoo4 (localhost [IPv6:::1]) by nightheron.gentoo.org (Postfix) with SMTP id 27A082019C; Wed, 10 Jan 2018 10:20:20 +0000 (UTC) Received: by lgentoo4 (sSMTP sendmail emulation); Wed, 10 Jan 2018 05:20:19 -0500 From: "root" Date: Wed, 10 Jan 2018 05:20:19 -0500 To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - stage1.spec Message-Id: <20180110102020.27A082019C@nightheron.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Reply-To: gentoo-releng-autobuilds@lists.gentoo.org X-Archives-Salt: 7a53f7fc-759d-4735-8221-2b97bd1e4f0a X-Archives-Hash: de56cbd388f0f144d38b9ba3980ad627 stage1 root path is /tmp/stage1root Source path set to /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2 Caching snapshot to /var/tmp/catalyst/snapshot_cache/20180110T101055Z/ The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180110T101055Z/ stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z/tmp/stage1root Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390x-20180110T101055Z/ Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390x-20180110T101055Z/ Checking for processes running in chroot and killing them. Removing AutoResume Points: ... Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180110T101055Z/ --- Running action sequence: unpack Referenced SEEDCACHE does not appear to be a directory, trying to untar... No Valid Resume point detected, cleaning up... Removing AutoResume Points: ... Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180110T101055Z/ Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z/ Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2 to /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z/ (This may take some time) ... tar: SELinux support is not available --- Running action sequence: unpack_snapshot Cleaning up invalid snapshot cache at /var/tmp/catalyst/snapshot_cache/20180110T101055Z/ (This can take a long time)... Unpacking portage tree (This can take a long time) ... tar: SELinux support is not available lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20180110T101055Z/.catalyst_lock' --- Running action sequence: setup_confdir Configuring /etc/portage... --- Running action sequence: portage_overlay --- Running action sequence: base_dirs --- Running action sequence: bind --- Running action sequence: chroot_setup Setting up chroot... Warning!!!! Overriding certain env variables may cause catastrophic failure. If your build fails look here first as the possible problem. Catalyst assumes you know what you are doing when setting these variables. Catalyst Maintainers use VERY minimal envscripts if used at all You have been warned --- Running action sequence: setup_environment --- Running action sequence: run_local copying make.conf to /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z///tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z//tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z//tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z/ >>> Regenerating /etc/ld.so.cache... Adding USE=' build' to make.conf for portage build emerge --quiet --oneshot --update --newuse sys-apps/portage Performing Global Updates (Could take a couple of minutes if you have a lot of binary packages.) The following packages are causing rebuilds: (app-arch/bzip2-1.0.6-r8:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) (sys-libs/zlib-1.2.11-r1:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-libs/libxml2-2.9.4-r1:2/2::gentoo, ebuild scheduled for merge) (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) !!! The following installed packages are masked: - sys-devel/binutils-2.26.1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Michał Górny , Andreas K. Hüttel , # Matthias Maier (21 May 2017) # These old versions of toolchain packages (binutils, gcc, glibc) are no # longer officially supported and are not suitable for general use. Using # these packages can result in build failures (and possible breakage) for # many packages, and may leave your system vulnerable to known security # exploits. # If you still use one of these old toolchain packages, please upgrade (and # switch the compiler / the binutils) ASAP. If you need them for a specific # (isolated) use case, feel free to unmask them on your system. # (updated 27 Dec 2017 with gcc < 5.4) - sys-devel/gcc-4.9.4::gentoo (masked by: package.mask) - sys-libs/glibc-2.23-r3::gentoo (masked by: package.mask) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. >>> Verifying ebuild manifests >>> Emerging (1 of 8) app-arch/bzip2-1.0.6-r8::gentoo >>> Installing (1 of 8) app-arch/bzip2-1.0.6-r8::gentoo >>> Emerging (2 of 8) app-portage/elt-patches-20170815::gentoo >>> Installing (2 of 8) app-portage/elt-patches-20170815::gentoo >>> Emerging (3 of 8) sys-libs/zlib-1.2.11-r1::gentoo >>> Installing (3 of 8) sys-libs/zlib-1.2.11-r1::gentoo >>> Emerging (4 of 8) dev-lang/python-2.7.14-r1::gentoo >>> Installing (4 of 8) dev-lang/python-2.7.14-r1::gentoo >>> Emerging (5 of 8) dev-libs/libxml2-2.9.4-r1::gentoo >>> Installing (5 of 8) dev-libs/libxml2-2.9.4-r1::gentoo >>> Emerging (6 of 8) dev-lang/python-3.4.5-r1::gentoo >>> Installing (6 of 8) dev-lang/python-3.4.5-r1::gentoo >>> Emerging (7 of 8) dev-lang/python-3.5.4-r1::gentoo >>> Installing (7 of 8) dev-lang/python-3.5.4-r1::gentoo >>> Emerging (8 of 8) sys-apps/portage-2.3.8::gentoo >>> Installing (8 of 8) sys-apps/portage-2.3.8::gentoo * Messages for package dev-lang/python-3.5.4-r1: * You have just upgraded from an older version of Python. * * Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules. Updating seed stage... emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc [ebuild U ] sys-apps/gentoo-functions-0.12 [0.10] [ebuild U ] app-text/sgml-common-0.6.3-r6 [0.6.3-r5] [ebuild U ] sys-devel/binutils-config-5-r4 [5-r3] [ebuild U ] dev-libs/libffi-3.2.1 [3.0.13-r1] [ebuild R ] sys-libs/cracklib-2.9.6-r1 [ebuild U ] sys-apps/file-5.32 [5.29] [ebuild U ] dev-libs/mpc-1.0.2-r1 [1.0.1] [ebuild U ] sys-apps/coreutils-8.26 [8.25] [ebuild U ] app-admin/eselect-1.4.8 [1.4.5] [ebuild R ] sys-kernel/linux-headers-4.4 [ebuild U ] dev-libs/openssl-1.0.2n [1.0.2k] [ebuild U ] dev-libs/expat-2.2.1 [2.2.0-r1] [ebuild U ] sys-devel/gettext-0.19.8.1 [0.19.7] [ebuild NS ] sys-devel/gcc-5.4.0-r4 [4.9.4] [ebuild U ] sys-libs/pam-1.2.1-r2 [1.2.1] [ebuild U ] app-text/docbook-xsl-stylesheets-1.79.1-r2 [1.79.1-r1] [ebuild U ] net-misc/rsync-3.1.2-r2 [3.1.2] [ebuild U ] dev-python/setuptools-36.0.1 [30.4.0] [ebuild R ] dev-python/certifi-2016.9.26 [ebuild R ] dev-python/pyxattr-0.5.5 [ebuild U ] app-admin/perl-cleaner-2.25 [2.20] The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by dev-python/certifi-2016.9.26::gentoo =dev-python/setuptools-36.0.1 ~s390 Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). Carefully examine the list of proposed changes, paying special attention to mask or keyword changes that may expose experimental or unstable packages. * In order to avoid wasting time, backtracking has terminated early * due to the above autounmask change(s). The --autounmask-backtrack=y * option can be used to force further backtracking, but there is no * guarantee that it will produce a solution. !!! The following installed packages are masked: - sys-devel/binutils-2.26.1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Michał Górny , Andreas K. Hüttel , # Matthias Maier (21 May 2017) # These old versions of toolchain packages (binutils, gcc, glibc) are no # longer officially supported and are not suitable for general use. Using # these packages can result in build failures (and possible breakage) for # many packages, and may leave your system vulnerable to known security # exploits. # If you still use one of these old toolchain packages, please upgrade (and # switch the compiler / the binutils) ASAP. If you need them for a specific # (isolated) use case, feel free to unmask them on your system. # (updated 27 Dec 2017 with gcc < 5.4) - sys-devel/gcc-4.9.4::gentoo (masked by: package.mask) - sys-libs/glibc-2.23-r3::gentoo (masked by: package.mask) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1244, in run_local "run script failed.",env=self.env) File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd raise CatalystError,myexc CatalystError None !!! catalyst: Stage build aborting due to error. Traceback (most recent call last): File "/usr/lib64/catalyst/catalyst", line 218, in build_target mytarget.run() File "modules/generic_stage_target.py", line 1304, in run apply(getattr(self,x)) File "modules/generic_stage_target.py", line 1249, in run_local raise CatalystError,"Stage build aborting due to error." CatalystError !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390x-20180110T101055Z/.catalyst_lock' Command exited with non-zero status 1 394.96user 81.35system 6:27.84elapsed 122%CPU (0avgtext+0avgdata 670448maxresident)k 0inputs+0outputs (614major+42842535minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20180110T101055Z.Vpw2BI/log/stage1.log