1 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: setup_confdir |
2 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: portage_overlay |
3 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: base_dirs |
4 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: bind |
5 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: chroot_setup |
6 |
02 Apr 2018 21:55:54 UTC: NOTICE : Setting up chroot... |
7 |
02 Apr 2018 21:55:54 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
8 |
02 Apr 2018 21:55:54 UTC: WARNING : If your build fails look here first as the possible problem. |
9 |
02 Apr 2018 21:55:54 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
10 |
02 Apr 2018 21:55:54 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
11 |
02 Apr 2018 21:55:54 UTC: WARNING : You have been warned. |
12 |
02 Apr 2018 21:55:54 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20180402T214502Z/etc/portage/make.conf |
13 |
02 Apr 2018 21:55:54 UTC: NOTICE : STICKY-CONFIG is enabled |
14 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: setup_environment |
15 |
02 Apr 2018 21:55:54 UTC: NOTICE : --- Running action sequence: run_local |
16 |
copying make.conf to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20180402T214502Z/tmp/stage1root/etc/portage |
17 |
Copying stage1-chroot.sh to /tmp |
18 |
copying stage1-chroot.sh to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20180402T214502Z/tmp |
19 |
copying chroot-functions.sh to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20180402T214502Z/tmp |
20 |
Ensure the file has the executable bit set |
21 |
Running stage1-chroot.sh in chroot: |
22 |
setarch linux32 chroot /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20180402T214502Z /tmp/stage1-chroot.sh |
23 |
>>> Regenerating /etc/ld.so.cache... |
24 |
Adding USE="${USE} build" to make.conf for portage build |
25 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
26 |
|
27 |
Performing Global Updates |
28 |
(Could take a couple of minutes if you have a lot of binary packages.) |
29 |
|
30 |
|
31 |
>>> Verifying ebuild manifests |
32 |
>>> Emerging (1 of 2) dev-lang/python-3.5.4-r1::gentoo |
33 |
>>> Installing (1 of 2) dev-lang/python-3.5.4-r1::gentoo |
34 |
>>> Emerging (2 of 2) sys-apps/portage-2.3.24-r1::gentoo |
35 |
>>> Installing (2 of 2) sys-apps/portage-2.3.24-r1::gentoo |
36 |
* Messages for package dev-lang/python-3.5.4-r1: |
37 |
* You have just upgraded from an older version of Python. |
38 |
* |
39 |
* Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules. |
40 |
|
41 |
|
42 |
Updating seed stage... |
43 |
emerge --quiet --buildpkg=n --update --deep @world |
44 |
|
45 |
|
46 |
[nomerge ] virtual/package-manager-1::gentoo [0::gentoo] |
47 |
[nomerge ] sys-apps/portage-2.3.24-r1::gentoo USE="build (ipc) native-extensions (xattr) -doc -epydoc -gentoo-dev -rsync-verify (-selinux)" PYTHON_TARGETS="python2_7 python3_5 -pypy -python3_4 -python3_6" |
48 |
[nomerge ] dev-python/pyxattr-0.5.5::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_5" |
49 |
[nomerge ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_5 -python3_6" |
50 |
[nomerge ] dev-python/six-1.11.0::gentoo [1.10.0::gentoo] USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" |
51 |
[nomerge ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" |
52 |
[ebuild R ] dev-python/certifi-2017.4.17::gentoo PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB |
53 |
[ebuild R ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB |
54 |
[ebuild R ] dev-python/packaging-16.8::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB |
55 |
[ebuild U ] dev-python/six-1.11.0::gentoo [1.10.0::gentoo] USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 30 KiB |
56 |
|
57 |
Total: 4 packages (1 upgrade, 3 reinstalls), Size of downloads: 30 KiB |
58 |
|
59 |
* Error: circular dependencies: |
60 |
|
61 |
(dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) depends on |
62 |
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, ebuild scheduled for merge) (buildtime) |
63 |
(dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) (buildtime) |
64 |
|
65 |
* Note that circular dependencies can often be avoided by temporarily |
66 |
* disabling USE flags that trigger optional dependencies. |
67 |
|
68 |
!!! Multiple package instances within a single package slot have been pulled |
69 |
!!! into the dependency graph, resulting in a slot conflict: |
70 |
|
71 |
sys-libs/readline:0 |
72 |
|
73 |
(sys-libs/readline-7.0_p3:0/7::gentoo, ebuild scheduled for merge) pulled in by |
74 |
>=sys-libs/readline-7.0:0= required by (app-shells/bash-4.4_p12:0/0::gentoo, ebuild scheduled for merge) |
75 |
^^ ^^^^^^ |
76 |
|
77 |
(sys-libs/readline-6.3_p8-r3:0/0::gentoo, installed) pulled in by |
78 |
sys-libs/readline:0/0= required by (sys-apps/gawk-4.1.4:0/0::gentoo, installed) |
79 |
^^^^^ |
80 |
(and 2 more with the same problem) |
81 |
|
82 |
dev-python/setuptools:0 |
83 |
|
84 |
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, installed) pulled in by |
85 |
(no parents that aren't satisfied by other packages in this slot) |
86 |
|
87 |
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by |
88 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/certifi-2017.4.17:0/0::gentoo, ebuild scheduled for merge) |
89 |
|
90 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) |
91 |
|
92 |
|
93 |
sys-libs/gdbm:0 |
94 |
|
95 |
(sys-libs/gdbm-1.13-r2:0/1.13::gentoo, ebuild scheduled for merge) pulled in by |
96 |
(no parents that aren't satisfied by other packages in this slot) |
97 |
|
98 |
(sys-libs/gdbm-1.11:0/0::gentoo, installed) pulled in by |
99 |
sys-libs/gdbm:0/0=[berkdb] required by (dev-lang/python-3.5.4-r1:3.5/3.5m::gentoo, installed) |
100 |
^^^^^ |
101 |
|
102 |
NOTE: Use the '--verbose-conflicts' option to display parents omitted above |
103 |
|
104 |
It may be possible to solve this problem by using package.mask to |
105 |
prevent one of those packages from being selected. However, it is also |
106 |
possible that conflicting dependencies exist such that they are |
107 |
impossible to satisfy simultaneously. If such a conflict exists in |
108 |
the dependencies of two different packages, then those packages can |
109 |
not be installed simultaneously. |
110 |
|
111 |
For more information, see MASKED PACKAGES section in the emerge man |
112 |
page or refer to the Gentoo Handbook. |
113 |
|
114 |
|
115 |
The following USE changes are necessary to proceed: |
116 |
(see "package.use" in the portage(5) man page for more details) |
117 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
118 |
# required by dev-python/six-1.11.0::gentoo |
119 |
# required by dev-python/packaging-16.8::gentoo |
120 |
>=dev-python/appdirs-1.4.3 python_targets_python3_4 |
121 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
122 |
# required by dev-python/six-1.11.0::gentoo |
123 |
# required by dev-python/packaging-16.8::gentoo |
124 |
>=dev-python/certifi-2017.4.17 python_targets_python3_4 |
125 |
# required by dev-python/packaging-16.8::gentoo |
126 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
127 |
# required by dev-python/six-1.11.0::gentoo |
128 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
129 |
# required by dev-python/pypax-0.9.2::gentoo |
130 |
# required by sys-apps/elfix-0.9.2::gentoo |
131 |
# required by @system |
132 |
# required by @world (argument) |
133 |
>=dev-python/pyparsing-2.2.0 python_targets_python3_4 |
134 |
# required by dev-python/six-1.11.0::gentoo |
135 |
# required by dev-python/packaging-16.8::gentoo |
136 |
>=dev-python/setuptools-34.0.2-r1 python_targets_python3_4 |
137 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
138 |
# required by dev-python/six-1.11.0::gentoo |
139 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
140 |
# required by dev-python/pypax-0.9.2::gentoo |
141 |
# required by sys-apps/elfix-0.9.2::gentoo |
142 |
# required by @system |
143 |
# required by @world (argument) |
144 |
>=dev-python/packaging-16.8 python_targets_python3_4 |
145 |
# required by dev-python/setuptools-34.0.2-r1::gentoo |
146 |
# required by dev-python/pypax-0.9.2::gentoo |
147 |
# required by sys-apps/elfix-0.9.2::gentoo |
148 |
# required by @system |
149 |
# required by @world (argument) |
150 |
>=dev-python/six-1.11.0 python_targets_python3_4 |
151 |
|
152 |
Use --autounmask-write to write changes to config files (honoring |
153 |
CONFIG_PROTECT). Carefully examine the list of proposed changes, |
154 |
paying special attention to mask or keyword changes that may expose |
155 |
experimental or unstable packages. |
156 |
|
157 |
* In order to avoid wasting time, backtracking has terminated early |
158 |
* due to the above autounmask change(s). The --autounmask-backtrack=y |
159 |
* option can be used to force further backtracking, but there is no |
160 |
* guarantee that it will produce a solution. |
161 |
|
162 |
!!! All ebuilds that could satisfy "dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]" have been masked. |
163 |
!!! One of the following masked packages is required to complete your request: |
164 |
- dev-python/setuptools-9999::gentoo (masked by: missing keyword) |
165 |
- dev-python/setuptools-38.5.1::gentoo (masked by: ~x86 keyword) |
166 |
- dev-python/setuptools-36.7.2::gentoo (masked by: ~x86 keyword) |
167 |
- dev-python/setuptools-36.0.1::gentoo (masked by: ~x86 keyword) |
168 |
- dev-python/setuptools-34.0.2-r1::gentoo (masked by: ) |
169 |
|
170 |
(dependency required by "dev-python/six-1.11.0::gentoo" [ebuild]) |
171 |
(dependency required by "dev-python/setuptools-34.0.2-r1::gentoo" [installed]) |
172 |
(dependency required by "dev-python/pypax-0.9.2::gentoo" [installed]) |
173 |
(dependency required by "sys-apps/elfix-0.9.2::gentoo" [installed]) |
174 |
(dependency required by "@system" [set]) |
175 |
(dependency required by "@world" [argument]) |
176 |
For more information, see the MASKED PACKAGES section in the emerge |
177 |
man page or refer to the Gentoo Handbook. |
178 |
|
179 |
02 Apr 2018 21:59:44 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
180 |
02 Apr 2018 21:59:45 UTC: ERROR : CatalystError: Stage build aborting due to error. |
181 |
02 Apr 2018 21:59:45 UTC: ERROR : Exception running action sequence run_local |
182 |
Traceback (most recent call last): |
183 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1354, in run_local |
184 |
env=self.env) |
185 |
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd |
186 |
print_traceback=False) |
187 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
188 |
|
189 |
During handling of the above exception, another exception occurred: |
190 |
|
191 |
Traceback (most recent call last): |
192 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1454, in run |
193 |
getattr(self, x)() |
194 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1363, in run_local |
195 |
print_traceback=False) |
196 |
catalyst.support.CatalystError: Stage build aborting due to error. |
197 |
02 Apr 2018 21:59:45 UTC: NOTICE : Cleaning up... Running unbind() |
198 |
Command exited with non-zero status 2 |
199 |
319.72user 80.72system 3:57.42elapsed 168%CPU (0avgtext+0avgdata 790656maxresident)k |
200 |
456056inputs+2608032outputs (0major+11537531minor)pagefaults 0swaps |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /release/tmp/run/catalyst-auto.20180402T214502Z.oiZDyL/log/hardened_stage1.log |