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 3D398138330 for ; Fri, 12 Jan 2018 04:53:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 72FD3E0984; Fri, 12 Jan 2018 04:53:01 +0000 (UTC) Received: from smtp.gentoo.org (mail.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 3F7D1E0984 for ; Fri, 12 Jan 2018 04:52:59 +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 1A89E335C4C; Fri, 12 Jan 2018 04:52:58 +0000 (UTC) Received: by nightheron.gentoo.org (Postfix, from userid 0) id 9327820354; Fri, 12 Jan 2018 04:52:56 +0000 (UTC) From: catalyst@nightheron.gentoo.org To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage1.spec Message-Id: <20180112045256.9327820354@nightheron.gentoo.org> Date: Fri, 12 Jan 2018 04:52:56 +0000 (UTC) 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: b626bb18-d7f1-41e1-851b-5f15246cb414 X-Archives-Hash: a473af1d4cad1afa936e845938082f82 12 Jan 2018 04:51:50 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf 12 Jan 2018 04:51:50 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'clear-autoresume', 'autoresume', 'snapcache', 'bindist', 'pkgcache', 'seedcache'} 12 Jan 2018 04:51:50 UTC: NOTICE : Processing spec file: hardened/stage1.spec 12 Jan 2018 04:51:50 UTC: NOTICE : Using target: stage1 12 Jan 2018 04:51:50 UTC: NOTICE : Source file specification matching setting is: loose 12 Jan 2018 04:51:50 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] 12 Jan 2018 04:51:52 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 12 Jan 2018 04:51:52 UTC: NOTICE : stage1 stage path is /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z/tmp/stage1root 12 Jan 2018 04:51:52 UTC: NOTICE : Removing AutoResume Points ... 12 Jan 2018 04:51:52 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage1-amd64-hardened-20180111T214502Z 12 Jan 2018 04:51:52 UTC: NOTICE : --- Running action sequence: unpack 12 Jan 2018 04:51:52 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar... 12 Jan 2018 04:51:52 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled 12 Jan 2018 04:51:52 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up... 12 Jan 2018 04:51:52 UTC: NOTICE : Removing AutoResume Points ... 12 Jan 2018 04:51:52 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage1-amd64-hardened-20180111T214502Z 12 Jan 2018 04:51:52 UTC: NOTICE : Clearing the chroot path ... 12 Jan 2018 04:51:52 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z 12 Jan 2018 04:51:52 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 12 Jan 2018 04:51:52 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z (this may take some time) .. 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: unpack_snapshot 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: setup_confdir 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: portage_overlay 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: base_dirs 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: bind 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: chroot_setup 12 Jan 2018 04:51:58 UTC: NOTICE : Setting up chroot... 12 Jan 2018 04:51:58 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. 12 Jan 2018 04:51:58 UTC: WARNING : If your build fails look here first as the possible problem. 12 Jan 2018 04:51:58 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. 12 Jan 2018 04:51:58 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. 12 Jan 2018 04:51:58 UTC: WARNING : You have been warned. 12 Jan 2018 04:51:58 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z/etc/portage/make.conf 12 Jan 2018 04:51:58 UTC: NOTICE : STICKY-CONFIG is enabled 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: setup_environment 12 Jan 2018 04:51:58 UTC: NOTICE : --- Running action sequence: run_local copying make.conf to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z/tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z/tmp copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z/tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot: chroot /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180111T214502Z /tmp/stage1-chroot.sh >>> Regenerating /etc/ld.so.cache... Adding USE="${USE} build" to make.conf for portage build emerge --quiet --oneshot --update --newuse sys-apps/portage >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/portage-2.3.13-r1::gentoo >>> Installing (1 of 1) sys-apps/portage-2.3.13-r1::gentoo Updating seed stage... emerge --quiet --buildpkg=n --update --deep @world [ebuild U ] sys-devel/gnuconfig-20170101 [20161104] [ebuild U ] sys-apps/man-pages-4.13 [4.09] [ebuild U ] app-editors/nano-2.8.7 [2.7.5] [ebuild U ] dev-perl/Locale-gettext-1.70.0 [1.50.0-r1] [ebuild NS ] sys-devel/autoconf-2.69-r4 [2.69] [uninstall ] sys-devel/autoconf-2.69 [blocks b ] ~sys-devel/autoconf-2.69:2.5 ("~sys-devel/autoconf-2.69:2.5" is blocking sys-devel/autoconf-2.69-r4) [ebuild U ] sys-libs/gdbm-1.13-r2 [1.11] !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-libs/gdbm:0 (sys-libs/gdbm-1.13-r2:0/1.13::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (sys-libs/gdbm-1.11:0/0::gentoo, installed) pulled in by sys-libs/gdbm:0/0=[berkdb] required by (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, installed) ^^^^^ (and 1 more with the same problem) NOTE: Use the '--verbose-conflicts' option to display parents omitted above The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by dev-lang/python-3.5.4-r1::gentoo[gdbm] # required by dev-python/certifi-2017.4.17::gentoo[python_targets_python3_5] # required by dev-python/setuptools-36.7.2::gentoo # required by dev-python/pyxattr-0.5.5::gentoo # required by sys-apps/portage-2.3.13-r1::gentoo[python_targets_python2_7] # required by virtual/package-manager-0::gentoo # required by @system # required by @world (argument) >=sys-libs/gdbm-1.13-r2 berkdb 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. 12 Jan 2018 04:52:56 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 12 Jan 2018 04:52:56 UTC: ERROR : CatalystError: Stage build aborting due to error. 12 Jan 2018 04:52:56 UTC: ERROR : Exception running action sequence run_local Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1354, in run_local env=self.env) File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd print_traceback=False) catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1454, in run getattr(self, x)() File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1363, in run_local print_traceback=False) catalyst.support.CatalystError: Stage build aborting due to error. 12 Jan 2018 04:52:56 UTC: NOTICE : Cleaning up... Running unbind() Command exited with non-zero status 2 57.92user 15.26system 1:05.80elapsed 111%CPU (0avgtext+0avgdata 1369216maxresident)k 86112inputs+2192040outputs (0major+1654225minor)pagefaults 0swaps Full build log at /release/tmp/run/catalyst-auto.20180111T214502Z.iwsrm6/log/hardened_stage1.log