*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage1-selinux-nomultilib.spec 17 Jun 2018 03:38:04 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf 17 Jun 2018 03:38:04 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'bindist', 'pkgcache', 'preserve_libs'} 17 Jun 2018 03:38:04 UTC: NOTICE : Processing spec file: hardened/stage1-selinux-nomultilib.spec 17 Jun 2018 03:38:04 UTC: NOTICE : Using target: stage1 17 Jun 2018 03:38:04 UTC: NOTICE : Source file specification matching setting is: loose 17 Jun 2018 03:38:04 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] 17 Jun 2018 03:38:04 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz 17 Jun 2018 03:38:04 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z/tmp/stage1root 17 Jun 2018 03:38:04 UTC: NOTICE : --- Running action sequence: unpack 17 Jun 2018 03:38:04 UTC: NOTICE : Clearing the chroot path ... 17 Jun 2018 03:38:04 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z 17 Jun 2018 03:38:04 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz 17 Jun 2018 03:38:04 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z (this may take some time) .. 17 Jun 2018 03:38:07 UTC: NOTICE : --- Running action sequence: unpack_snapshot 17 Jun 2018 03:38:07 UTC: NOTICE : Unpacking portage tree (this can take a long time) ... 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: setup_confdir 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: portage_overlay 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: base_dirs 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: bind 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: chroot_setup 17 Jun 2018 03:38:22 UTC: NOTICE : Setting up chroot... 17 Jun 2018 03:38:22 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. 17 Jun 2018 03:38:22 UTC: WARNING : If your build fails look here first as the possible problem. 17 Jun 2018 03:38:22 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. 17 Jun 2018 03:38:22 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. 17 Jun 2018 03:38:22 UTC: WARNING : You have been warned. 17 Jun 2018 03:38:22 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z/etc/portage/make.conf 17 Jun 2018 03:38:22 UTC: NOTICE : STICKY-CONFIG is enabled 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: setup_environment 17 Jun 2018 03:38:22 UTC: NOTICE : --- Running action sequence: run_local copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z/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-20180616T013251Z/tmp copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180616T013251Z/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-20180616T013251Z /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.) [ebuild U ] sys-libs/libsepol-2.8 [2.7] [ebuild U ] sys-devel/automake-1.15.1-r2 [1.15-r2] [ebuild NS ] dev-lang/python-3.5.5 [2.7.14, 3.4.5] [ebuild U ] sys-libs/libselinux-2.8 [2.7] [ebuild U ] sys-apps/portage-2.3.40-r1 [2.3.8] !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-libs/libselinux:0 (sys-libs/libselinux-2.8:0/0::gentoo, ebuild scheduled for merge) pulled in by >=sys-libs/libselinux-2.0.94[python,python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/portage-2.3.40-r1:0/0::gentoo, ebuild scheduled for merge) (sys-libs/libselinux-2.7:0/0::gentoo, installed) pulled in by >=sys-libs/libselinux-2.7:0/0=[python,python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (sys-apps/policycoreutils-2.7:0/0::gentoo, installed) >=sys-libs/libselinux-2.7:0/0=[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (app-admin/setools-4.1.1:0/0::gentoo, installed) >=sys-libs/libselinux-2.7:=[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (app-admin/setools-4.1.1:0/0::gentoo, installed) >=sys-libs/libselinux-2.7:=[python,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/policycoreutils-2.7:0/0::gentoo, installed) The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by sys-libs/libselinux-2.7::gentoo # required by @system # required by @world (argument) =sys-libs/libsepol-2.8 ~amd64 # required by sys-apps/shadow-4.5::gentoo # required by virtual/shadow-0::gentoo # required by @system # required by @world (argument) =sys-libs/libselinux-2.8 ~amd64 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-libs/glibc-2.25-r8::gentoo (masked by: package.mask) /var/gentoo/repos/gentoo/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/binutils-2.28.1::gentoo (masked by: package.mask) - sys-devel/gcc-5.4.0-r3::gentoo (masked by: package.mask) /var/gentoo/repos/gentoo/profiles/releases/17.0/package.mask: # Andreas K. Huettel (27 May 2017) # In the 17.0 profiles we assume that our system compiler uses C++14 # or later as default language setting. This means it has to be at # least GCC 6. If you need an older compiler for specific purposes, # feel free to unmask it, however, using it for normal emerging of # packages is neither recommended nor supported in any way. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. 17 Jun 2018 03:38:29 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 17 Jun 2018 03:38:29 UTC: ERROR : CatalystError: Stage build aborting due to error. 17 Jun 2018 03:38:29 UTC: ERROR : Exception running action sequence run_local Traceback (most recent call last): File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1354, in run_local env=self.env) File "/usr/lib64/python3.5/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.5/site-packages/catalyst/base/stagebase.py", line 1454, in run getattr(self, x)() File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1363, in run_local print_traceback=False) catalyst.support.CatalystError: Stage build aborting due to error. 17 Jun 2018 03:38:29 UTC: NOTICE : Cleaning up... Running unbind() Command exited with non-zero status 2 30.24user 3.78system 0:25.45elapsed 133%CPU (0avgtext+0avgdata 351672maxresident)k 0inputs+3441664outputs (0major+269032minor)pagefaults 0swaps Full build log at /home/release/tmp/run/catalyst-auto.20180616T013251Z.G9U5R9/log/hardened_stage1-selinux-nomultilib.log