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