| 1 |
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-nomultilib.spec |
| 2 |
02 Mar 2019 17:19:08 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf |
| 3 |
02 Mar 2019 17:19:08 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'preserve_libs', 'pkgcache', 'bindist'} |
| 4 |
02 Mar 2019 17:19:08 UTC: NOTICE : Processing spec file: hardened/stage1-nomultilib.spec |
| 5 |
02 Mar 2019 17:19:08 UTC: NOTICE : Using target: stage1 |
| 6 |
02 Mar 2019 17:19:08 UTC: NOTICE : Source file specification matching setting is: loose |
| 7 |
02 Mar 2019 17:19:08 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] |
| 8 |
02 Mar 2019 17:19:09 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz |
| 9 |
02 Mar 2019 17:19:09 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z/tmp/stage1root |
| 10 |
02 Mar 2019 17:19:09 UTC: NOTICE : --- Running action sequence: unpack |
| 11 |
02 Mar 2019 17:19:09 UTC: NOTICE : Clearing the chroot path ... |
| 12 |
02 Mar 2019 17:19:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z |
| 13 |
02 Mar 2019 17:19:09 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz |
| 14 |
02 Mar 2019 17:19:09 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z (this may take some time) .. |
| 15 |
02 Mar 2019 17:19:12 UTC: NOTICE : --- Running action sequence: unpack_snapshot |
| 16 |
02 Mar 2019 17:19:12 UTC: NOTICE : Unpacking portage tree (this can take a long time) ... |
| 17 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: setup_confdir |
| 18 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: portage_overlay |
| 19 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: base_dirs |
| 20 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: bind |
| 21 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: chroot_setup |
| 22 |
02 Mar 2019 17:19:25 UTC: NOTICE : Setting up chroot... |
| 23 |
02 Mar 2019 17:19:25 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
| 24 |
02 Mar 2019 17:19:25 UTC: WARNING : If your build fails look here first as the possible problem. |
| 25 |
02 Mar 2019 17:19:25 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
| 26 |
02 Mar 2019 17:19:25 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
| 27 |
02 Mar 2019 17:19:25 UTC: WARNING : You have been warned. |
| 28 |
02 Mar 2019 17:19:25 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z/etc/portage/make.conf |
| 29 |
02 Mar 2019 17:19:25 UTC: NOTICE : STICKY-CONFIG is enabled |
| 30 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: setup_environment |
| 31 |
02 Mar 2019 17:19:25 UTC: NOTICE : --- Running action sequence: run_local |
| 32 |
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z/tmp/stage1root/etc/portage |
| 33 |
Copying stage1-chroot.sh to /tmp |
| 34 |
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z/tmp |
| 35 |
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z/tmp |
| 36 |
Ensure the file has the executable bit set |
| 37 |
Running stage1-chroot.sh in chroot: |
| 38 |
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190302T162037Z /tmp/stage1-chroot.sh |
| 39 |
>>> Regenerating /etc/ld.so.cache... |
| 40 |
Adding USE="${USE} build" to make.conf for portage build |
| 41 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
| 42 |
|
| 43 |
Performing Global Updates |
| 44 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 45 |
|
| 46 |
|
| 47 |
>>> Verifying ebuild manifests |
| 48 |
>>> Emerging (1 of 1) sys-apps/portage-2.3.51-r1::gentoo |
| 49 |
>>> Failed to emerge sys-apps/portage-2.3.51-r1, Log file: |
| 50 |
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171928.log' |
| 51 |
* Package: sys-apps/portage-2.3.51-r1 |
| 52 |
* Repository: gentoo |
| 53 |
* Maintainer: dev-portage@g.o |
| 54 |
* Upstream: dev-portage@g.o |
| 55 |
* USE: abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify userland_GNU xattr |
| 56 |
* FEATURES: preserve-libs sandbox userpriv usersandbox |
| 57 |
* Please follow the instructions in the news item: |
| 58 |
* 2017-12-26-experimental-amd64-17-1-profiles |
| 59 |
* or choose the 17.0 profile. |
| 60 |
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase): |
| 61 |
* ERROR: 17.1 migration has not been performed!! |
| 62 |
* |
| 63 |
* Call stack: |
| 64 |
* ebuild.sh, line 610: Called __source_all_bashrcs |
| 65 |
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' |
| 66 |
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' |
| 67 |
* profile.bashrc, line 6: Called die |
| 68 |
* The specific snippet of code: |
| 69 |
* die "ERROR: 17.1 migration has not been performed!!" |
| 70 |
* |
| 71 |
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`, |
| 72 |
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`. |
| 73 |
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171928.log'. |
| 74 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'. |
| 75 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/die.env'. |
| 76 |
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir' |
| 77 |
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51' |
| 78 |
* Messages for package sys-apps/portage-2.3.51-r1: |
| 79 |
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171928.log |
| 80 |
* Please follow the instructions in the news item: |
| 81 |
* 2017-12-26-experimental-amd64-17-1-profiles |
| 82 |
* or choose the 17.0 profile. |
| 83 |
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase): |
| 84 |
* ERROR: 17.1 migration has not been performed!! |
| 85 |
* |
| 86 |
* Call stack: |
| 87 |
* ebuild.sh, line 610: Called __source_all_bashrcs |
| 88 |
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' |
| 89 |
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' |
| 90 |
* profile.bashrc, line 6: Called die |
| 91 |
* The specific snippet of code: |
| 92 |
* die "ERROR: 17.1 migration has not been performed!!" |
| 93 |
* |
| 94 |
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`, |
| 95 |
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`. |
| 96 |
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171928.log'. |
| 97 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'. |
| 98 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/die.env'. |
| 99 |
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir' |
| 100 |
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51' |
| 101 |
|
| 102 |
|
| 103 |
02 Mar 2019 17:19:29 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 104 |
02 Mar 2019 17:19:30 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 105 |
02 Mar 2019 17:19:30 UTC: ERROR : Exception running action sequence run_local |
| 106 |
Traceback (most recent call last): |
| 107 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local |
| 108 |
env=self.env) |
| 109 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 110 |
print_traceback=False) |
| 111 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 112 |
|
| 113 |
During handling of the above exception, another exception occurred: |
| 114 |
|
| 115 |
Traceback (most recent call last): |
| 116 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1455, in run |
| 117 |
getattr(self, x)() |
| 118 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local |
| 119 |
print_traceback=False) |
| 120 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 121 |
02 Mar 2019 17:19:30 UTC: NOTICE : Cleaning up... Running unbind() |
| 122 |
Command exited with non-zero status 2 |
| 123 |
28.08user 3.92system 0:21.84elapsed 146%CPU (0avgtext+0avgdata 353132maxresident)k |
| 124 |
0inputs+3338832outputs (0major+488576minor)pagefaults 0swaps |
| 125 |
|
| 126 |
|
| 127 |
|
| 128 |
Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/hardened_stage1-nomultilib.log |
Archives