1 |
Distributed under the GNU General Public License version 2.1 |
2 |
|
3 |
Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf |
4 |
Setting sharedir to config file value "/usr/lib64/catalyst" |
5 |
Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache" |
6 |
Setting hash_function to config file value "crc32" |
7 |
Setting storedir to config file value "/var/tmp/catalyst" |
8 |
Setting portdir to config file value "/usr/portage" |
9 |
Setting distdir to config file value "/usr/portage/distfiles" |
10 |
Setting options to config file value "autoresume bindist kerncache pkgcache seedcache snapcache" |
11 |
Autoresuming support enabled. |
12 |
Binary redistribution enabled |
13 |
Kernel cache support enabled. |
14 |
Package cache support enabled. |
15 |
Seed cache support enabled. |
16 |
Snapshot cache support enabled. |
17 |
Envscript support enabled. |
18 |
Using target: netboot2 |
19 |
Building natively for s390 |
20 |
Source path set to /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2 |
21 |
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20181024T091439Z/ |
22 |
The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20181024T091439Z/ |
23 |
Location of the package cache is /var/tmp/catalyst/packages/default/netboot2-s390x-20181024T091439Z/ |
24 |
Location of the kerncache is /var/tmp/catalyst/kerncache/default/netboot2-s390x-20181024T091439Z/ |
25 |
Checking for processes running in chroot and killing them. |
26 |
Removing AutoResume Points: ... |
27 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20181024T091439Z/ |
28 |
--- Running action sequence: unpack |
29 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
30 |
No Valid Resume point detected, cleaning up... |
31 |
Removing AutoResume Points: ... |
32 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20181024T091439Z/ |
33 |
Emptying directory /var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z/ |
34 |
|
35 |
Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2 |
36 |
to /var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z/ (This may take some time) ... |
37 |
|
38 |
tar: SELinux support is not available |
39 |
--- Running action sequence: unpack_snapshot |
40 |
Valid snapshot cache, skipping unpack of portage tree... |
41 |
--- Running action sequence: config_profile_link |
42 |
Configuring profile link... |
43 |
--- Running action sequence: setup_confdir |
44 |
Configuring /etc/portage... |
45 |
--- Running action sequence: portage_overlay |
46 |
--- Running action sequence: bind |
47 |
--- Running action sequence: chroot_setup |
48 |
Setting up chroot... |
49 |
|
50 |
Warning!!!! |
51 |
Overriding certain env variables may cause catastrophic failure. |
52 |
If your build fails look here first as the possible problem. |
53 |
Catalyst assumes you know what you are doing when setting |
54 |
these variables. |
55 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
56 |
You have been warned |
57 |
|
58 |
|
59 |
Warning!!! |
60 |
The use of -* in netboot2/use will cause portage to ignore |
61 |
package.use in the profile and portage_confdir. You've been warned! |
62 |
--- Running action sequence: setup_environment |
63 |
--- Running action sequence: build_packages |
64 |
>>> Building packages ... |
65 |
Copying netboot2-pkg.sh to /tmp |
66 |
copying netboot2-pkg.sh to /var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z//tmp |
67 |
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z//tmp |
68 |
Ensure the file has the executable bit set |
69 |
Running netboot2-pkg.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z/ |
70 |
>>> Regenerating /etc/ld.so.cache... |
71 |
>>> Regenerating /etc/ld.so.cache... |
72 |
emerge --quiet --usepkg --buildpkg --newuse sys-apps/s390-tools sys-fs/e2fsprogs sys-apps/util-linux app-editors/nano sys-libs/ncurses dev-libs/popt net-misc/wget net-misc/rsync dev-libs/libtommath net-misc/dropbear dev-libs/openssl app-misc/screen sys-devel/bc |
73 |
|
74 |
Performing Global Updates |
75 |
(Could take a couple of minutes if you have a lot of binary packages.) |
76 |
|
77 |
|
78 |
>>> Verifying ebuild manifests |
79 |
>>> Emerging (1 of 13) sys-libs/ncurses-6.1-r2::gentoo |
80 |
>>> Failed to emerge sys-libs/ncurses-6.1-r2, Log file: |
81 |
>>> '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/build.log' |
82 |
* Package: sys-libs/ncurses-6.1-r2 |
83 |
* Repository: gentoo |
84 |
* Maintainer: base-system@g.o |
85 |
* USE: abi_s390_64 elibc_glibc kernel_linux s390 unicode userland_GNU |
86 |
* FEATURES: preserve-libs sandbox userpriv usersandbox |
87 |
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work': No such file or directory |
88 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
89 |
* ERROR: sys-libs/ncurses-6.1-r2::gentoo failed (unpack phase): |
90 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
91 |
* Failed to create dir '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work' |
92 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
93 |
* |
94 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
95 |
* Call stack: |
96 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
97 |
* ebuild.sh, line 792: Called __ebuild_main 'unpack' |
98 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
99 |
* phase-functions.sh, line 1067: Called __dyn_unpack |
100 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
101 |
* phase-functions.sh, line 251: Called die |
102 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
103 |
* The specific snippet of code: |
104 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
105 |
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'" |
106 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
107 |
* |
108 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
109 |
* If you need support, post the output of `emerge --info '=sys-libs/ncurses-6.1-r2::gentoo'`, |
110 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
111 |
* the complete build log and the output of `emerge -pqv '=sys-libs/ncurses-6.1-r2::gentoo'`. |
112 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
113 |
* The complete build log is located at '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/build.log'. |
114 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
115 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/environment'. |
116 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
117 |
* Working directory: '/var/tmp/portage/sys-libs/ncurses-6.1-r2/homedir' |
118 |
/usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device |
119 |
* S: '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work/ncurses-6.1' |
120 |
* ACCESS DENIED: open_wr: /usr/lib64/python3.5/site-packages/7bwrzy08 |
121 |
Traceback (most recent call last): |
122 |
File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 277, in <module> |
123 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
124 |
File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 273, in ebuild_ipc_main |
125 |
return ebuild_ipc.communicate(args) |
126 |
File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 130, in communicate |
127 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
128 |
File "/usr/lib64/python3.5/site-packages/portage/locks.py", line 194, in lockfile |
129 |
locking_method = portage._eintr_func_wrapper(_get_lock_fn()) |
130 |
File "/usr/lib64/python3.5/site-packages/portage/locks.py", line 62, in _get_lock_fn |
131 |
fd, lock_path = tempfile.mkstemp() |
132 |
File "/usr/lib64/python3.5/tempfile.py", line 335, in mkstemp |
133 |
prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir) |
134 |
File "/usr/lib64/python3.5/tempfile.py", line 130, in _sanitize_params |
135 |
dir = gettempdir() |
136 |
File "/usr/lib64/python3.5/tempfile.py", line 296, in gettempdir |
137 |
tempdir = _get_default_tempdir() |
138 |
File "/usr/lib64/python3.5/tempfile.py", line 231, in _get_default_tempdir |
139 |
dirlist) |
140 |
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp', '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp', '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.5/site-packages'] |
141 |
* --------------------------- ACCESS VIOLATION SUMMARY --------------------------- |
142 |
* LOG FILE: "/var/log/sandbox/sandbox-22618.log" |
143 |
* -------------------------------------------------------------------------------- |
144 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
145 |
* is known to be triggered by things such as failed variable assignments |
146 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
147 |
* exiting, bash should have displayed an error message above. If bash did |
148 |
* not produce an error message above, it's possible that the ebuild has |
149 |
* called `exit` when it should have called `die` instead. This behavior |
150 |
* may also be triggered by a corrupt bash binary or a hardware problem |
151 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
152 |
* it appears to occur randomly, then it is likely to be triggered by a |
153 |
* hardware problem. If you suspect a hardware problem then you should try |
154 |
* some basic hardware diagnostics such as memtest. Please do not report |
155 |
* this as a bug unless it is consistently reproducible and you are sure |
156 |
* that your bash binary and hardware are functioning properly. |
157 |
* Messages for package sys-libs/ncurses-6.1-r2: |
158 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
159 |
* is known to be triggered by things such as failed variable assignments |
160 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
161 |
* exiting, bash should have displayed an error message above. If bash did |
162 |
* not produce an error message above, it's possible that the ebuild has |
163 |
* called `exit` when it should have called `die` instead. This behavior |
164 |
* may also be triggered by a corrupt bash binary or a hardware problem |
165 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
166 |
* it appears to occur randomly, then it is likely to be triggered by a |
167 |
* hardware problem. If you suspect a hardware problem then you should try |
168 |
* some basic hardware diagnostics such as memtest. Please do not report |
169 |
* this as a bug unless it is consistently reproducible and you are sure |
170 |
* that your bash binary and hardware are functioning properly. |
171 |
|
172 |
|
173 |
|
174 |
!!! catalyst: Error in attempt to build packages |
175 |
|
176 |
|
177 |
Traceback (most recent call last): |
178 |
File "modules/generic_stage_target.py", line 1403, in build_packages |
179 |
"Error in attempt to build packages",env=self.env) |
180 |
File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd |
181 |
raise CatalystError,myexc |
182 |
CatalystError |
183 |
None |
184 |
|
185 |
!!! catalyst: netboot2build aborting due to error. |
186 |
|
187 |
Traceback (most recent call last): |
188 |
File "/usr/lib64/catalyst/catalyst", line 218, in build_target |
189 |
mytarget.run() |
190 |
File "modules/generic_stage_target.py", line 1304, in run |
191 |
apply(getattr(self,x)) |
192 |
File "modules/generic_stage_target.py", line 1408, in build_packages |
193 |
"build aborting due to error." |
194 |
CatalystError |
195 |
!!! catalyst: Error encountered during run of target netboot2 |
196 |
Catalyst aborting.... |
197 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/netboot2-s390x-20181024T091439Z/.catalyst_lock' |
198 |
Command exited with non-zero status 1 |
199 |
21.50user 2.13system 0:30.90elapsed 76%CPU (0avgtext+0avgdata 258448maxresident)k |
200 |
0inputs+0outputs (25major+328838minor)pagefaults 0swaps |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.20181024T091439Z.BVs5YK/log/netboot_netboot.log |