From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-releng-autobuilds+bounces-9362-garchives=archives.gentoo.org@lists.gentoo.org>
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 C94BD138334
for <garchives@archives.gentoo.org>; Sat, 2 Mar 2019 16:17:19 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 0C284E0885;
Sat, 2 Mar 2019 16:17:19 +0000 (UTC)
Received: from thor.jmbsvicetto.name (thor.jmbsvicetto.name [136.243.173.91])
(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 C2EE9E0885
for <gentoo-releng-autobuilds@lists.gentoo.org>; Sat, 2 Mar 2019 16:17:18 +0000 (UTC)
Received: by thor.jmbsvicetto.name (Postfix, from userid 0)
id 68C9161BA1; Sat, 2 Mar 2019 16:17:17 +0000 (UTC)
From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
Message-Id: <20190302161717.68C9161BA1@thor.jmbsvicetto.name>
Date: Sat, 2 Mar 2019 16:17:17 +0000 (UTC)
Precedence: bulk
List-Post: <mailto:gentoo-releng-autobuilds@lists.gentoo.org>
List-Help: <mailto:gentoo-releng-autobuilds+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-releng-autobuilds+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-releng-autobuilds+subscribe@lists.gentoo.org>
List-Id: Gentoo Release Engineering Autobuilds <gentoo-releng-autobuilds.gentoo.org>
X-BeenThere: gentoo-releng-autobuilds@gentoo.org
X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org
Reply-To: gentoo-releng-autobuilds@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
X-Archives-Salt: 1c804b8a-5527-4903-a6d3-de71ff35ec50
X-Archives-Hash: a1f1e6563374dbdf7084e49d97009b99
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 16:16:20 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:16:20 UTC: NOTICE : conf_values[options] = {'bindist', 'preserve_libs', 'pkgcache', 'clear-autoresume'}
02 Mar 2019 16:16:20 UTC: NOTICE : Processing spec file: hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 16:16:20 UTC: NOTICE : Using target: stage1
02 Mar 2019 16:16:20 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:16:20 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
02 Mar 2019 16:16:21 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 16:16:21 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp/stage1root
02 Mar 2019 16:16:21 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:16:21 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:16:21 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z
02 Mar 2019 16:16:21 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 16:16:21 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z (this may take some time) ..
02 Mar 2019 16:16:31 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:16:31 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: base_dirs
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:17:11 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:17:11 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:17:11 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:17:11 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:17:11 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:17:11 UTC: WARNING : You have been warned.
02 Mar 2019 16:17:11 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/etc/portage/make.conf
02 Mar 2019 16:17:11 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:17:11 UTC: NOTICE : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z /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.)
* Last emerge --sync was 210d 3h 12m 13s ago.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.40-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'
* Package: sys-apps/portage-2.3.40-r1
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify selinux userland_GNU xattr
* FEATURES: preserve-libs sandbox selinux sesandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
* Messages for package sys-apps/portage-2.3.40-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
02 Mar 2019 16:17:16 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
02 Mar 2019 16:17:17 UTC: ERROR : CatalystError: Stage build aborting due to error.
02 Mar 2019 16:17:17 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
env=self.env)
File "/usr/lib64/python3.6/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.6/site-packages/catalyst/base/stagebase.py", line 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
02 Mar 2019 16:17:17 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.02user 4.37system 0:56.48elapsed 60%CPU (0avgtext+0avgdata 352632maxresident)k
1560inputs+3637392outputs (0major+524016minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/hardened_stage1-selinux-nomultilib.log