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 9A4131382C5 for ; Fri, 18 May 2018 09:16:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A09C0E0809; Fri, 18 May 2018 09:16:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 6B68CE0809 for ; Fri, 18 May 2018 09:16:04 +0000 (UTC) Received: from nightheron.gentoo.org (nightheron.gentoo.org [154.52.129.26]) (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 89BCD335C2E; Fri, 18 May 2018 09:16:02 +0000 (UTC) Received: from lgentoo4 (localhost [IPv6:::1]) by nightheron.gentoo.org (Postfix) with SMTP id B03902026A; Fri, 18 May 2018 09:16:00 +0000 (UTC) Received: by lgentoo4 (sSMTP sendmail emulation); Fri, 18 May 2018 05:16:00 -0400 From: "root" Date: Fri, 18 May 2018 05:16:00 -0400 To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - stage1.spec Message-Id: <20180518091600.B03902026A@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: b41b1e85-30b2-4419-b99a-7326c8f376b0 X-Archives-Hash: e7cc5828cfdcb09e6a9f5a62e3c0c838 *** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f stage1.spec Catalyst, version 2.0.18 Copyright 2003-2008 Gentoo Foundation Copyright 2008-2012 various authors Distributed under the GNU General Public License version 2.1 Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf Setting sharedir to config file value "/usr/lib64/catalyst" Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache" Setting hash_function to config file value "crc32" Setting storedir to config file value "/var/tmp/catalyst" Setting portdir to config file value "/usr/portage" Setting distdir to config file value "/usr/portage/distfiles" Setting options to config file value "autoresume bindist kerncache pkgcache seedcache snapcache" Autoresuming support enabled. Binary redistribution enabled Kernel cache support enabled. Package cache support enabled. Seed cache support enabled. Snapshot cache support enabled. Envscript support enabled. Using target: stage1 Building natively for s390 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/20180518T091252Z/ The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180518T091252Z/ stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z/tmp/stage1root Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390x-20180518T091252Z/ Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390x-20180518T091252Z/ Checking for processes running in chroot and killing them. Removing AutoResume Points: ... Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180518T091252Z/ --- 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-20180518T091252Z/ Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z/ Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2 to /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z/ (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/20180518T091252Z/ (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/20180518T091252Z/.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-20180518T091252Z///tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z//tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z//tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390x-20180518T091252Z/ >>> 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.) >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/portage-2.3.8::gentoo >>> Installing (1 of 1) sys-apps/portage-2.3.8::gentoo Updating seed stage... emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc The following packages are causing rebuilds: (sys-libs/readline-7.0_p3:0/7::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) (sys-libs/gdbm-1.13-r2:0/1.13::gentoo, ebuild scheduled for merge) (dev-lang/python-3.5.4-r1:3.5/3.5m::gentoo, ebuild scheduled for merge) (sys-apps/util-linux-2.30.2-r1:0/0::gentoo, ebuild scheduled for merge) (app-shells/bash-4.4_p12:0/0::gentoo, ebuild scheduled for merge) (dev-libs/libpcre-8.42:3/3::gentoo, ebuild scheduled for merge) (sys-apps/gawk-4.1.4:0/0::gentoo, ebuild scheduled for merge) (dev-libs/libxml2-2.9.7:2/2::gentoo, ebuild scheduled for merge) [ebuild U ] sys-libs/ncurses-6.1-r2 [6.0-r1] [ebuild U ] dev-lang/python-exec-2.4.5 [2.4.4] [ebuild U ] sys-devel/autoconf-wrapper-13-r1 [13] [ebuild U ] sys-apps/debianutils-4.8.3 [4.7] [ebuild U ] app-admin/eselect-1.4.11 [1.4.8] [ebuild U ] app-eselect/eselect-python-20171204 [20160516] [ebuild U ] app-arch/xz-utils-5.2.3 [5.2.2] [ebuild U ] sys-devel/flex-2.6.4-r1 [2.6.1] [ebuild r U ] sys-libs/readline-7.0_p3 [6.3_p8-r3] [ebuild U ] net-misc/rsync-3.1.3 [3.1.2-r2] [ebuild U ] app-misc/pax-utils-1.2.3 [1.1.7] [ebuild rR ] sys-apps/util-linux-2.30.2-r1 [ebuild U ] app-shells/bash-4.4_p12 [4.3_p48-r1] [ebuild r U ] sys-apps/gawk-4.1.4 [4.1.3] [ebuild r U ] dev-libs/libpcre-8.42 [8.40-r1] [ebuild U ] sys-apps/sandbox-2.13 [2.10-r4] [ebuild U ] virtual/perl-ExtUtils-MakeMaker-7.100.200_rc-r4 [7.100.200_rc-r3] [ebuild U ] dev-lang/perl-5.24.3-r1 [5.24.3] [ebuild U ] sys-devel/automake-1.15.1-r2 [1.15.1-r1] [ebuild rR ] dev-libs/libxml2-2.9.7 [ebuild rR ] sys-libs/gdbm-1.13-r2 [ebuild rR ] dev-lang/python-3.5.4-r1 [ebuild rR ] dev-lang/python-2.7.14-r1 [ebuild U ] dev-libs/libxslt-1.1.32 [1.1.30-r2] [ebuild U ] dev-python/six-1.11.0 [1.10.0] [ebuild U ] app-misc/ca-certificates-20170717.3.36.1 [20161130.3.30.2] [ebuild R ] sys-apps/portage-2.3.8 The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by dev-libs/glib-2.50.3-r1::gentoo # required by x11-misc/shared-mime-info-1.4::gentoo =dev-libs/libpcre-8.42 ~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. !!! 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-20180518T091252Z/.catalyst_lock' Command exited with non-zero status 1 43.16user 9.24system 1:00.19elapsed 87%CPU (0avgtext+0avgdata 288976maxresident)k 0inputs+0outputs (434major+1897500minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20180518T091252Z.efcAuW/log/stage1.log