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 7280A138331 for ; Mon, 15 Jan 2018 10:18:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9DCA8E089D; Mon, 15 Jan 2018 10:18:14 +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 6EE66E089D for ; Mon, 15 Jan 2018 10:18:13 +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 F15B1335C46; Mon, 15 Jan 2018 10:18:11 +0000 (UTC) Received: by nightheron.gentoo.org (Postfix, from userid 0) id 689BA2046F; Mon, 15 Jan 2018 10:18:10 +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: <20180115101810.689BA2046F@nightheron.gentoo.org> Date: Mon, 15 Jan 2018 10:18:10 +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: 88f7615c-6937-4296-86f3-5cfa1e47dc31 X-Archives-Hash: 1192ffe072b4c7fa8136566d2f09f32c 15 Jan 2018 10:17:01 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf 15 Jan 2018 10:17:01 UTC: NOTICE : conf_values[options] = {'autoresume', 'seedcache', 'clear-autoresume', 'bindist', 'preserve_libs', 'pkgcache', 'snapcache'} 15 Jan 2018 10:17:01 UTC: NOTICE : Processing spec file: hardened/stage1.spec 15 Jan 2018 10:17:01 UTC: NOTICE : Using target: stage1 15 Jan 2018 10:17:01 UTC: NOTICE : Source file specification matching setting is: loose 15 Jan 2018 10:17:01 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] 15 Jan 2018 10:17:02 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 15 Jan 2018 10:17:02 UTC: NOTICE : stage1 stage path is /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z/tmp/stage1root 15 Jan 2018 10:17:02 UTC: NOTICE : Removing AutoResume Points ... 15 Jan 2018 10:17:02 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage1-amd64-hardened-20180114T214501Z 15 Jan 2018 10:17:02 UTC: NOTICE : --- Running action sequence: unpack 15 Jan 2018 10:17:02 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar... 15 Jan 2018 10:17:02 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled 15 Jan 2018 10:17:02 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up... 15 Jan 2018 10:17:02 UTC: NOTICE : Removing AutoResume Points ... 15 Jan 2018 10:17:02 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage1-amd64-hardened-20180114T214501Z 15 Jan 2018 10:17:02 UTC: NOTICE : Clearing the chroot path ... 15 Jan 2018 10:17:02 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z 15 Jan 2018 10:17:02 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 15 Jan 2018 10:17:02 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z (this may take some time) .. 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: unpack_snapshot 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: setup_confdir 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: portage_overlay 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: base_dirs 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: bind 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: chroot_setup 15 Jan 2018 10:17:07 UTC: NOTICE : Setting up chroot... 15 Jan 2018 10:17:07 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. 15 Jan 2018 10:17:07 UTC: WARNING : If your build fails look here first as the possible problem. 15 Jan 2018 10:17:07 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. 15 Jan 2018 10:17:07 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. 15 Jan 2018 10:17:07 UTC: WARNING : You have been warned. 15 Jan 2018 10:17:07 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z/etc/portage/make.conf 15 Jan 2018 10:17:07 UTC: NOTICE : STICKY-CONFIG is enabled 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: setup_environment 15 Jan 2018 10:17:07 UTC: NOTICE : --- Running action sequence: run_local copying make.conf to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z/tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z/tmp copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-20180114T214501Z/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-20180114T214501Z /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 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.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 ] sys-devel/gcc-6.4.0-r1 [6.4.0] [ebuild U ] virtual/libelf-3 [1] [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-3.5.4-r1:3.5/3.5m::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/pyxattr-0.5.5::gentoo[python_targets_python3_5] # required by sys-apps/portage-2.3.13-r1::gentoo[python_targets_python2_7] # required by app-admin/perl-cleaner-2.25::gentoo # required by dev-lang/perl-5.24.3::gentoo # required by dev-perl/Locale-gettext-1.70.0::gentoo # required by sys-apps/help2man-1.47.4::gentoo[nls] # required by sys-devel/automake-1.15.1-r1::gentoo # required by dev-libs/libxslt-1.1.30-r2::gentoo # required by dev-libs/glib-2.50.3-r1::gentoo # required by x11-misc/shared-mime-info-1.9::gentoo >=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. 15 Jan 2018 10:18:10 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 15 Jan 2018 10:18:10 UTC: ERROR : CatalystError: Stage build aborting due to error. 15 Jan 2018 10:18:10 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. 15 Jan 2018 10:18:10 UTC: NOTICE : Cleaning up... Running unbind() Command exited with non-zero status 2 59.82user 15.31system 1:09.03elapsed 108%CPU (0avgtext+0avgdata 1369632maxresident)k 266512inputs+2192048outputs (0major+1654094minor)pagefaults 0swaps Full build log at /release/tmp/run/catalyst-auto.20180114T214501Z.SrT8AI/log/hardened_stage1.log