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