| 1 |
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage1-selinux-nomultilib.spec |
| 2 |
28 May 2018 15:08:50 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf |
| 3 |
28 May 2018 15:08:50 UTC: NOTICE : conf_values[options] = {'bindist', 'pkgcache', 'preserve_libs', 'clear-autoresume'} |
| 4 |
28 May 2018 15:08:50 UTC: NOTICE : Processing spec file: hardened/stage1-selinux-nomultilib.spec |
| 5 |
28 May 2018 15:08:50 UTC: NOTICE : Using target: stage1 |
| 6 |
28 May 2018 15:08:50 UTC: NOTICE : Source file specification matching setting is: loose |
| 7 |
28 May 2018 15:08:50 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] |
| 8 |
28 May 2018 15:08:50 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz |
| 9 |
28 May 2018 15:08:50 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z/tmp/stage1root |
| 10 |
28 May 2018 15:08:50 UTC: NOTICE : --- Running action sequence: unpack |
| 11 |
28 May 2018 15:08:50 UTC: NOTICE : Clearing the chroot path ... |
| 12 |
28 May 2018 15:08:50 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z |
| 13 |
28 May 2018 15:08:50 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz |
| 14 |
28 May 2018 15:08:50 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z (this may take some time) .. |
| 15 |
28 May 2018 15:08:54 UTC: NOTICE : --- Running action sequence: unpack_snapshot |
| 16 |
28 May 2018 15:08:54 UTC: NOTICE : Unpacking portage tree (this can take a long time) ... |
| 17 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: setup_confdir |
| 18 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: portage_overlay |
| 19 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: base_dirs |
| 20 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: bind |
| 21 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: chroot_setup |
| 22 |
28 May 2018 15:09:04 UTC: NOTICE : Setting up chroot... |
| 23 |
28 May 2018 15:09:04 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
| 24 |
28 May 2018 15:09:04 UTC: WARNING : If your build fails look here first as the possible problem. |
| 25 |
28 May 2018 15:09:04 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
| 26 |
28 May 2018 15:09:04 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
| 27 |
28 May 2018 15:09:04 UTC: WARNING : You have been warned. |
| 28 |
28 May 2018 15:09:04 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z/etc/portage/make.conf |
| 29 |
28 May 2018 15:09:04 UTC: NOTICE : STICKY-CONFIG is enabled |
| 30 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: setup_environment |
| 31 |
28 May 2018 15:09:04 UTC: NOTICE : --- Running action sequence: run_local |
| 32 |
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z/tmp/stage1root/etc/portage |
| 33 |
Copying stage1-chroot.sh to /tmp |
| 34 |
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z/tmp |
| 35 |
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z/tmp |
| 36 |
Ensure the file has the executable bit set |
| 37 |
Running stage1-chroot.sh in chroot: |
| 38 |
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180528T030004Z /tmp/stage1-chroot.sh |
| 39 |
>>> Regenerating /etc/ld.so.cache... |
| 40 |
Adding USE="${USE} build" to make.conf for portage build |
| 41 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
| 42 |
|
| 43 |
Performing Global Updates |
| 44 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 45 |
|
| 46 |
|
| 47 |
[ebuild U ] sys-libs/libsepol-2.8 [2.7] |
| 48 |
[ebuild U ] sys-devel/automake-1.15.1-r2 [1.15-r2] |
| 49 |
[ebuild NS ] dev-lang/python-3.5.5 [2.7.14, 3.4.5] |
| 50 |
[ebuild U ] sys-libs/libselinux-2.8 [2.7] |
| 51 |
[ebuild U ] sys-apps/portage-2.3.24-r1 [2.3.8] |
| 52 |
|
| 53 |
!!! Multiple package instances within a single package slot have been pulled |
| 54 |
!!! into the dependency graph, resulting in a slot conflict: |
| 55 |
|
| 56 |
sys-libs/libselinux:0 |
| 57 |
|
| 58 |
(sys-libs/libselinux-2.8:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 59 |
>=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.24-r1:0/0::gentoo, ebuild scheduled for merge) |
| 60 |
|
| 61 |
|
| 62 |
(sys-libs/libselinux-2.7:0/0::gentoo, installed) pulled in by |
| 63 |
>=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) |
| 64 |
|
| 65 |
>=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) |
| 66 |
|
| 67 |
>=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) |
| 68 |
|
| 69 |
>=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) |
| 70 |
|
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
The following keyword changes are necessary to proceed: |
| 75 |
(see "package.accept_keywords" in the portage(5) man page for more details) |
| 76 |
# required by sys-libs/libselinux-2.7::gentoo |
| 77 |
# required by @system |
| 78 |
# required by @world (argument) |
| 79 |
=sys-libs/libsepol-2.8 ~amd64 |
| 80 |
# required by sys-apps/shadow-4.5::gentoo |
| 81 |
# required by virtual/shadow-0::gentoo |
| 82 |
# required by @system |
| 83 |
# required by @world (argument) |
| 84 |
=sys-libs/libselinux-2.8 ~amd64 |
| 85 |
|
| 86 |
Use --autounmask-write to write changes to config files (honoring |
| 87 |
CONFIG_PROTECT). Carefully examine the list of proposed changes, |
| 88 |
paying special attention to mask or keyword changes that may expose |
| 89 |
experimental or unstable packages. |
| 90 |
|
| 91 |
* In order to avoid wasting time, backtracking has terminated early |
| 92 |
* due to the above autounmask change(s). The --autounmask-backtrack=y |
| 93 |
* option can be used to force further backtracking, but there is no |
| 94 |
* guarantee that it will produce a solution. |
| 95 |
|
| 96 |
!!! The following installed packages are masked: |
| 97 |
- sys-libs/glibc-2.25-r8::gentoo (masked by: package.mask) |
| 98 |
/var/gentoo/repos/gentoo/profiles/package.mask: |
| 99 |
# Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, |
| 100 |
# Matthias Maier <tamiko@g.o> (21 May 2017) |
| 101 |
# These old versions of toolchain packages (binutils, gcc, glibc) are no |
| 102 |
# longer officially supported and are not suitable for general use. Using |
| 103 |
# these packages can result in build failures (and possible breakage) for |
| 104 |
# many packages, and may leave your system vulnerable to known security |
| 105 |
# exploits. |
| 106 |
# If you still use one of these old toolchain packages, please upgrade (and |
| 107 |
# switch the compiler / the binutils) ASAP. If you need them for a specific |
| 108 |
# (isolated) use case, feel free to unmask them on your system. |
| 109 |
# (updated 27 Dec 2017 with gcc < 5.4) |
| 110 |
|
| 111 |
- sys-devel/binutils-2.28.1::gentoo (masked by: package.mask) |
| 112 |
- sys-devel/gcc-5.4.0-r3::gentoo (masked by: package.mask) |
| 113 |
/var/gentoo/repos/gentoo/profiles/releases/17.0/package.mask: |
| 114 |
# Andreas K. Huettel <dilfridge@g.o> (27 May 2017) |
| 115 |
# In the 17.0 profiles we assume that our system compiler uses C++14 |
| 116 |
# or later as default language setting. This means it has to be at |
| 117 |
# least GCC 6. If you need an older compiler for specific purposes, |
| 118 |
# feel free to unmask it, however, using it for normal emerging of |
| 119 |
# packages is neither recommended nor supported in any way. |
| 120 |
|
| 121 |
For more information, see the MASKED PACKAGES section in the emerge |
| 122 |
man page or refer to the Gentoo Handbook. |
| 123 |
|
| 124 |
28 May 2018 15:09:11 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 125 |
28 May 2018 15:09:11 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 126 |
28 May 2018 15:09:11 UTC: ERROR : Exception running action sequence run_local |
| 127 |
Traceback (most recent call last): |
| 128 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1354, in run_local |
| 129 |
env=self.env) |
| 130 |
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd |
| 131 |
print_traceback=False) |
| 132 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 133 |
|
| 134 |
During handling of the above exception, another exception occurred: |
| 135 |
|
| 136 |
Traceback (most recent call last): |
| 137 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1454, in run |
| 138 |
getattr(self, x)() |
| 139 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1363, in run_local |
| 140 |
print_traceback=False) |
| 141 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 142 |
28 May 2018 15:09:11 UTC: NOTICE : Cleaning up... Running unbind() |
| 143 |
Command exited with non-zero status 2 |
| 144 |
30.25user 3.66system 0:21.54elapsed 157%CPU (0avgtext+0avgdata 351504maxresident)k |
| 145 |
0inputs+3464072outputs (0major+265251minor)pagefaults 0swaps |
| 146 |
|
| 147 |
|
| 148 |
|
| 149 |
Full build log at /home/release/tmp/run/catalyst-auto.20180528T030004Z.F2Ma7Y/log/hardened_stage1-selinux-nomultilib.log |
Archives