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