1 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/binhost-snapshot to 755 |
2 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/chmod-lite to 755 |
3 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/isolated-functions.sh to 755 |
4 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/socks5-server.py to 755 |
5 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/install.py to 755 |
6 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/chmod-lite.py to 755 |
7 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/filter-bash-environment.py to 755 |
8 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/eapi.sh to 755 |
9 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/clean_locks to 755 |
10 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/glsa-check to 755 |
11 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/dohtml.py to 755 |
12 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/xpak-helper.py to 755 |
13 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/save-ebuild-env.sh to 755 |
14 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/ebuild.sh to 755 |
15 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/python3.4/lock-helper.py to 755 |
16 |
running install_scripts_sbin |
17 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/etc-update -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
18 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/archive-conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
19 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/emaint -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
20 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/env-update -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
21 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/fixpackages -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
22 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/dispatch-conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
23 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/scripts/sbin/regenworld -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4 |
24 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/etc-update to 755 |
25 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/archive-conf to 755 |
26 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/emaint to 755 |
27 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/env-update to 755 |
28 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/fixpackages to 755 |
29 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/dispatch-conf to 755 |
30 |
changing mode of /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/python-exec/python3.4/regenworld to 755 |
31 |
running install_data |
32 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share |
33 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man |
34 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man/man5 |
35 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ebuild.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man5 |
36 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/make.conf.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man5 |
37 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/portage.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man5 |
38 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/xpak.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man5 |
39 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/color.map.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man5 |
40 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man/man1 |
41 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ebuild.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
42 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/etc-update.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
43 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/emaint.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
44 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/emerge.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
45 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/quickpkg.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
46 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/dispatch-conf.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
47 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/emirrordist.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
48 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/repoman.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
49 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/env-update.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
50 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/egencache.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
51 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/fixpackages.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/man1 |
52 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man/ru |
53 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man/ru/man5 |
54 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/color.map.5 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man5 |
55 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/man/ru/man1 |
56 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/ebuild.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man1 |
57 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/etc-update.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man1 |
58 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/dispatch-conf.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man1 |
59 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/env-update.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man1 |
60 |
copying /var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24-python3_4/man/ru/fixpackages.1 -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/man/ru/man1 |
61 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/etc |
62 |
copying cnf/etc-update.conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/etc |
63 |
copying cnf/dispatch-conf.conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/etc |
64 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/etc/logrotate.d |
65 |
copying cnf/logrotate.d/elog-save-summary -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/etc/logrotate.d |
66 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/portage |
67 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/portage/config |
68 |
copying cnf/make.conf.example -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/portage/config |
69 |
copying cnf/make.globals -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/portage/config |
70 |
copying cnf/repos.conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/portage/config |
71 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/portage/config/sets |
72 |
copying cnf/sets/portage.conf -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/portage/config/sets |
73 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/doc |
74 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/share/doc/portage-2.2.24 |
75 |
copying NEWS -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/doc/portage-2.2.24 |
76 |
copying RELEASE-NOTES -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/share/doc/portage-2.2.24 |
77 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/usr/lib/portage/bin |
78 |
copying bin/deprecated-path -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib/portage/bin |
79 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/etc/portage |
80 |
creating /var/tmp/portage/sys-apps/portage-2.2.24/image/_python3.4/etc/portage/repo.postsync.d |
81 |
copying cnf/repo.postsync.d/example -> /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/etc/portage/repo.postsync.d |
82 |
running install_egg_info |
83 |
Writing /var/tmp/portage/sys-apps/portage-2.2.24/image//_python3.4/usr/lib64/python3.4/site-packages/portage-2.2.24-py3.4.egg-info |
84 |
* python3_4: running distutils-r1_run_phase python_install_all |
85 |
* Moving admin scripts to the correct directory |
86 |
* Moving /usr/bin/archive-conf to /usr/sbin/archive-conf |
87 |
* Moving /usr/bin/dispatch-conf to /usr/sbin/dispatch-conf |
88 |
* Moving /usr/bin/emaint to /usr/sbin/emaint |
89 |
* Moving /usr/bin/env-update to /usr/sbin/env-update |
90 |
* Moving /usr/bin/etc-update to /usr/sbin/etc-update |
91 |
* Moving /usr/bin/fixpackages to /usr/sbin/fixpackages |
92 |
* Moving /usr/bin/regenworld to /usr/sbin/regenworld |
93 |
* |
94 |
* This release of portage contains the new repoman code base |
95 |
* This code base is still being developed. So its API's are |
96 |
* not to be considered stable and are subject to change. |
97 |
* The code released has been tested and considered ready for use. |
98 |
* This however does not guarantee it to be completely bug free. |
99 |
* Please report any bugs you may encounter. |
100 |
* |
101 |
/var/tmp/portage/._portage_reinstall_.cyzbp9of/bin/phase-functions.sh: line 137: /usr/bin/python3.4: No such file or directory |
102 |
* ERROR: sys-apps/portage-2.2.24::gentoo failed (postinst phase): |
103 |
* filter-bash-environment.py failed |
104 |
* |
105 |
* Call stack: |
106 |
* ebuild.sh, line 765: Called __ebuild_main 'postinst' |
107 |
* phase-functions.sh, line 904: Called __filter_readonly_variables '--filter-path' '--filter-sandbox' '--allow-extra-vars' |
108 |
* phase-functions.sh, line 137: Called die |
109 |
* The specific snippet of code: |
110 |
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" |
111 |
* |
112 |
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.24::gentoo'`, |
113 |
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.24::gentoo'`. |
114 |
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.2.24:20151218-025347.log'. |
115 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.2.24/temp/build.log'. |
116 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.24/temp/environment'. |
117 |
* Working directory: '/var/tmp/portage/._portage_reinstall_.cyzbp9of/pym' |
118 |
* S: '/var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24' |
119 |
/var/tmp/portage/._portage_reinstall_.cyzbp9of/bin/ebuild-ipc: line 9: /usr/bin/python3.4: No such file or directory |
120 |
* The ebuild phase 'postinst' has exited unexpectedly. This type of |
121 |
* behavior is known to be triggered by things such as failed variable |
122 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
123 |
* Normally, before exiting, bash should have displayed an error message |
124 |
* above. If bash did not produce an error message above, it's possible |
125 |
* that the ebuild has called `exit` when it should have called `die` |
126 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
127 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
128 |
* not reproducible or it appears to occur randomly, then it is likely to |
129 |
* be triggered by a hardware problem. If you suspect a hardware problem |
130 |
* then you should try some basic hardware diagnostics such as memtest. |
131 |
* Please do not report this as a bug unless it is consistently |
132 |
* reproducible and you are sure that your bash binary and hardware are |
133 |
* functioning properly. |
134 |
[Errno 2] No such file or directory: b'/usr/bin/sandbox': |
135 |
/usr/bin/sandbox /var/tmp/portage/._portage_reinstall_.cyzbp9of/bin/misc-functions.sh die_hooks |
136 |
Traceback (most recent call last): |
137 |
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 317, in spawn |
138 |
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 515, in _exec |
139 |
File "/usr/lib64/python3.4/site-packages/portage/__init__.py", line 259, in __call__ |
140 |
FileNotFoundError: [Errno 2] No such file or directory: b'/usr/bin/sandbox' |
141 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
142 |
* behavior is known to be triggered by things such as failed variable |
143 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
144 |
* Normally, before exiting, bash should have displayed an error message |
145 |
* above. If bash did not produce an error message above, it's possible |
146 |
* that the ebuild has called `exit` when it should have called `die` |
147 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
148 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
149 |
* not reproducible or it appears to occur randomly, then it is likely to |
150 |
* be triggered by a hardware problem. If you suspect a hardware problem |
151 |
* then you should try some basic hardware diagnostics such as memtest. |
152 |
* Please do not report this as a bug unless it is consistently |
153 |
* reproducible and you are sure that your bash binary and hardware are |
154 |
* functioning properly. |
155 |
* FAILED postinst: 1 |
156 |
* Messages for package sys-apps/portage-2.2.24: |
157 |
* The ebuild phase 'postinst' has exited unexpectedly. This type of |
158 |
* behavior is known to be triggered by things such as failed variable |
159 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
160 |
* Normally, before exiting, bash should have displayed an error message |
161 |
* above. If bash did not produce an error message above, it's possible |
162 |
* that the ebuild has called `exit` when it should have called `die` |
163 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
164 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
165 |
* not reproducible or it appears to occur randomly, then it is likely to |
166 |
* be triggered by a hardware problem. If you suspect a hardware problem |
167 |
* then you should try some basic hardware diagnostics such as memtest. |
168 |
* Please do not report this as a bug unless it is consistently |
169 |
* reproducible and you are sure that your bash binary and hardware are |
170 |
* functioning properly. |
171 |
* FAILED postinst: 1 |
172 |
* ERROR: sys-apps/portage-2.2.24::gentoo failed (postinst phase): |
173 |
* filter-bash-environment.py failed |
174 |
* |
175 |
* Call stack: |
176 |
* ebuild.sh, line 765: Called __ebuild_main 'postinst' |
177 |
* phase-functions.sh, line 904: Called __filter_readonly_variables '--filter-path' '--filter-sandbox' '--allow-extra-vars' |
178 |
* phase-functions.sh, line 137: Called die |
179 |
* The specific snippet of code: |
180 |
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" |
181 |
* |
182 |
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.24::gentoo'`, |
183 |
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.24::gentoo'`. |
184 |
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.2.24:20151218-025347.log'. |
185 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.2.24/temp/build.log'. |
186 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.24/temp/environment'. |
187 |
* Working directory: '/var/tmp/portage/._portage_reinstall_.cyzbp9of/pym' |
188 |
* S: '/var/tmp/portage/sys-apps/portage-2.2.24/work/portage-2.2.24' |
189 |
|
190 |
|
191 |
18 Dec 2015 02:58:58 UTC: ERROR : CatalystError: cmd() NON-zero return value from: run script failed. |
192 |
18 Dec 2015 02:58:58 UTC: ERROR : CatalystError: Stage build aborting due to error. |
193 |
18 Dec 2015 02:58:58 UTC: ERROR : Exception running action sequence run_local |
194 |
Traceback (most recent call last): |
195 |
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1397, in run |
196 |
getattr(self, x)() |
197 |
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1309, in run_local |
198 |
print_traceback=False) |
199 |
CatalystError |
200 |
18 Dec 2015 02:58:58 UTC: NOTICE : Cleaning up... Running unbind() |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /home/release/tmp/run/catalyst-auto.sFygJC/log/stage1-nomultilib.log |