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 B68AD138330 for ; Thu, 11 Jan 2018 08:21:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BBCFEE0C0E; Thu, 11 Jan 2018 08:21:43 +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 854CEE0C0E for ; Thu, 11 Jan 2018 08:21:41 +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 B1793335C48; Thu, 11 Jan 2018 08:21:39 +0000 (UTC) Received: from lgentoo3 (localhost [IPv6:::1]) by nightheron.gentoo.org (Postfix) with SMTP id C7A7120249; Thu, 11 Jan 2018 08:21:37 +0000 (UTC) Received: by lgentoo3 (sSMTP sendmail emulation); Thu, 11 Jan 2018 03:21:37 -0500 From: "root" Date: Thu, 11 Jan 2018 03:21:37 -0500 To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [s390-auto] Catalyst fatal build error - stage1.spec Message-Id: <20180111082137.C7A7120249@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: 030fc066-b341-4196-9b6a-57238f0ad298 X-Archives-Hash: a293bbcdd5665a89c074c8963370ccd0 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-s390-20180111T081044Z///tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20180111T081044Z//tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20180111T081044Z//tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390-20180111T081044Z/ >>> 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: (sys-libs/zlib-1.2.11-r1:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) (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) (app-arch/bzip2-1.0.6-r8:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) !!! The following installed packages are masked: - sys-devel/gcc-4.9.4::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-libs/glibc-2.23-r3::gentoo (masked by: package.mask) - sys-devel/binutils-2.26.1::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 [nomerge ] virtual/package-manager-0::gentoo [nomerge ] sys-apps/portage-2.3.8::gentoo USE="(ipc) native-extensions xattr -build -doc -epydoc (-selinux)" PYTHON_TARGETS="python2_7 python3_5 (-pypy) -python3_4 -python3_6" [nomerge ] dev-python/pyxattr-0.5.5::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_5* (-pypy) -python3_4*" [nomerge ] dev-python/setuptools-34.0.2-r1::gentoo [30.4.0::gentoo] USE="{-test}" PYTHON_TARGETS="python2_7 python3_5* (-pypy) (-pypy3) -python3_4* -python3_6" [ebuild R ] dev-python/certifi-2016.9.26::gentoo PYTHON_TARGETS="python2_7 python3_5* (-pypy) (-pypy3) -python3_4* -python3_6" 0 KiB [ebuild N ~] dev-python/packaging-16.8::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 44 KiB [ebuild R ] dev-python/pyxattr-0.5.5::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_5* (-pypy) -python3_4*" 0 KiB [nomerge ] dev-python/packaging-16.8::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" [ebuild N ~] dev-python/six-1.11.0::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 30 KiB [ebuild U ] dev-python/setuptools-34.0.2-r1::gentoo [30.4.0::gentoo] USE="{-test}" PYTHON_TARGETS="python2_7 python3_5* (-pypy) (-pypy3) -python3_4* -python3_6" 604 KiB Total: 5 packages (1 upgrade, 2 new, 2 reinstalls), Size of downloads: 677 KiB * Error: circular dependencies: (dev-python/setuptools-34.0.2-r1:0/0::gentoo, ebuild scheduled for merge) depends on (dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) (buildtime) (dev-python/setuptools-34.0.2-r1:0/0::gentoo, ebuild scheduled for merge) (buildtime) * Note that circular dependencies can often be avoided by temporarily * disabling USE flags that trigger optional dependencies. 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/setuptools-34.0.2-r1::gentoo # required by dev-python/pyxattr-0.5.5::gentoo # required by sys-apps/portage-2.3.8::gentoo[xattr,python_targets_python2_7] # required by app-admin/perl-cleaner-2.25::gentoo # required by dev-lang/perl-5.22.3_rc4::gentoo # required by sys-kernel/linux-headers-4.4::gentoo # required by virtual/os-headers-0::gentoo # required by sys-libs/glibc-2.25-r9::gentoo # required by sys-devel/gcc-5.4.0-r4::gentoo # required by @system # required by @world (argument) =dev-python/six-1.11.0 ~s390 # required by dev-python/setuptools-34.0.2-r1::gentoo # required by dev-python/pyxattr-0.5.5::gentoo # required by sys-apps/portage-2.3.8::gentoo[xattr,python_targets_python2_7] # required by app-admin/perl-cleaner-2.25::gentoo # required by dev-lang/perl-5.22.3_rc4::gentoo # required by sys-kernel/linux-headers-4.4::gentoo # required by virtual/os-headers-0::gentoo # required by sys-libs/glibc-2.25-r9::gentoo # required by sys-devel/gcc-5.4.0-r4::gentoo # required by @system # required by @world (argument) =dev-python/packaging-16.8 ~s390 # required by dev-python/setuptools-34.0.2-r1::gentoo # required by dev-python/pyxattr-0.5.5::gentoo # required by sys-apps/portage-2.3.8::gentoo[xattr,python_targets_python2_7] # required by app-admin/perl-cleaner-2.25::gentoo # required by dev-lang/perl-5.22.3_rc4::gentoo # required by sys-kernel/linux-headers-4.4::gentoo # required by virtual/os-headers-0::gentoo # required by sys-libs/glibc-2.25-r9::gentoo # required by sys-devel/gcc-5.4.0-r4::gentoo # required by @system # required by @world (argument) =dev-python/appdirs-1.4.3 ~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) 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/lib/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/lib/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-s390-20180111T081044Z/.catalyst_lock' Command exited with non-zero status 1 420.79user 80.50system 7:21.03elapsed 113%CPU (0avgtext+0avgdata 465056maxresident)k 0inputs+0outputs (571major+37400833minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20180111T081044Z.8Rss0u/log/stage1.log