1 |
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec |
2 |
08 Jan 2023 05:05:25 UTC: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf |
3 |
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf |
4 |
08 Jan 2023 05:05:25 UTC: NOTICE : conf_values[options] = ['bindist', 'pkgcache', 'seedcache', 'clear-autoresume'] |
5 |
NOTICE:catalyst:conf_values[options] = ['bindist', 'pkgcache', 'seedcache', 'clear-autoresume'] |
6 |
08 Jan 2023 05:05:25 UTC: NOTICE : Processing spec file: /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec |
7 |
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec |
8 |
08 Jan 2023 05:05:25 UTC: NOTICE : Using target: stage1 |
9 |
NOTICE:catalyst:Using target: stage1 |
10 |
08 Jan 2023 05:05:25 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2'] |
11 |
NOTICE:catalyst:Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2'] |
12 |
08 Jan 2023 05:05:25 UTC: NOTICE : Source path set to /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz |
13 |
NOTICE:catalyst:Source path set to /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz |
14 |
08 Jan 2023 05:05:25 UTC: NOTICE : --- Running action sequence: unpack |
15 |
NOTICE:catalyst:--- Running action sequence: unpack |
16 |
08 Jan 2023 05:05:25 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
17 |
NOTICE:catalyst:Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
18 |
08 Jan 2023 05:05:25 UTC: NOTICE : Clearing the chroot path ... |
19 |
NOTICE:catalyst:Clearing the chroot path ... |
20 |
08 Jan 2023 05:05:25 UTC: NOTICE : Starting auto from /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz |
21 |
NOTICE:catalyst:Starting auto from /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz |
22 |
08 Jan 2023 05:05:25 UTC: NOTICE : to /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z (this may take some time) .. |
23 |
NOTICE:catalyst:to /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z (this may take some time) .. |
24 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: config_profile_link |
25 |
NOTICE:catalyst:--- Running action sequence: config_profile_link |
26 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: setup_confdir |
27 |
NOTICE:catalyst:--- Running action sequence: setup_confdir |
28 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: process_repos |
29 |
NOTICE:catalyst:--- Running action sequence: process_repos |
30 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: bind |
31 |
NOTICE:catalyst:--- Running action sequence: bind |
32 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: chroot_setup |
33 |
NOTICE:catalyst:--- Running action sequence: chroot_setup |
34 |
08 Jan 2023 05:05:34 UTC: NOTICE : Setting up chroot... |
35 |
NOTICE:catalyst:Setting up chroot... |
36 |
08 Jan 2023 05:05:34 UTC: NOTICE : Copying binary interpreter /usr/bin/qemu-riscv64 into chroot |
37 |
NOTICE:catalyst:Copying binary interpreter /usr/bin/qemu-riscv64 into chroot |
38 |
08 Jan 2023 05:05:34 UTC: WARNING : env variables in catalystrc may cause catastrophic failure. |
39 |
WARNING:catalyst:env variables in catalystrc may cause catastrophic failure. |
40 |
08 Jan 2023 05:05:34 UTC: WARNING : If your build fails look here first as the possible problem. |
41 |
WARNING:catalyst:If your build fails look here first as the possible problem. |
42 |
08 Jan 2023 05:05:34 UTC: NOTICE : Writing the stage make.conf to: /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z/etc/portage/make.conf |
43 |
NOTICE:catalyst:Writing the stage make.conf to: /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z/etc/portage/make.conf |
44 |
08 Jan 2023 05:05:34 UTC: NOTICE : STICKY-CONFIG is enabled |
45 |
NOTICE:catalyst:STICKY-CONFIG is enabled |
46 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: setup_environment |
47 |
NOTICE:catalyst:--- Running action sequence: setup_environment |
48 |
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: run_local |
49 |
NOTICE:catalyst:--- Running action sequence: run_local |
50 |
Running chroot.sh in chroot: |
51 |
chroot /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z /tmp/chroot.sh |
52 |
>>> Regenerating /etc/ld.so.cache... |
53 |
Updating seed stage... |
54 |
emerge --quiet --jobs 10 --load-average 32.0 --buildpkg=n -uDN @world |
55 |
|
56 |
Performing Global Updates |
57 |
(Could take a couple of minutes if you have a lot of binary packages.) |
58 |
|
59 |
|
60 |
>>> Verifying ebuild manifests |
61 |
>>> Running pre-merge checks for net-misc/openssh-9.1_p1-r2 |
62 |
>>> Running pre-merge checks for sys-apps/portage-3.0.43 |
63 |
* Determining the location of the kernel source code |
64 |
* Unable to find kernel sources at /usr/src/linux |
65 |
* Please make sure that /usr/src/linux points at your running kernel, |
66 |
* (or the kernel you wish to build against). |
67 |
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location |
68 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
69 |
* Checking for suitable kernel configuration options ... |
70 |
[ ok ] |
71 |
>>> Emerging (1 of 20) sys-libs/ncurses-6.4::gentoo |
72 |
>>> Emerging (2 of 20) sys-devel/gcc-config-2.10::gentoo |
73 |
>>> Emerging (3 of 20) sys-devel/binutils-config-5.5::gentoo |
74 |
>>> Installing (2 of 20) sys-devel/gcc-config-2.10::gentoo |
75 |
>>> Installing (3 of 20) sys-devel/binutils-config-5.5::gentoo |
76 |
>>> Installing (1 of 20) sys-libs/ncurses-6.4::gentoo |
77 |
>>> Emerging (4 of 20) app-alternatives/sh-0::gentoo |
78 |
>>> Emerging (5 of 20) sys-apps/file-5.44-r1::gentoo |
79 |
>>> Installing (4 of 20) app-alternatives/sh-0::gentoo |
80 |
>>> Installing (5 of 20) sys-apps/file-5.44-r1::gentoo |
81 |
>>> Emerging (6 of 20) dev-db/sqlite-3.40.1::gentoo |
82 |
>>> Installing (6 of 20) dev-db/sqlite-3.40.1::gentoo |
83 |
>>> Emerging (7 of 20) sys-apps/kmod-30-r1::gentoo |
84 |
>>> Emerging (8 of 20) sys-apps/texinfo-7.0.1-r1::gentoo |
85 |
>>> Installing (8 of 20) sys-apps/texinfo-7.0.1-r1::gentoo |
86 |
>>> Installing (7 of 20) sys-apps/kmod-30-r1::gentoo |
87 |
>>> Emerging (9 of 20) net-misc/openssh-9.1_p1-r2::gentoo |
88 |
>>> Emerging (10 of 20) app-misc/ca-certificates-20211016.3.87::gentoo |
89 |
>>> Installing (10 of 20) app-misc/ca-certificates-20211016.3.87::gentoo |
90 |
>>> Installing (9 of 20) net-misc/openssh-9.1_p1-r2::gentoo |
91 |
>>> Emerging (11 of 20) sys-fs/e2fsprogs-1.46.5-r4::gentoo |
92 |
>>> Emerging (12 of 20) dev-python/typing-extensions-4.4.0::gentoo |
93 |
>>> Installing (12 of 20) dev-python/typing-extensions-4.4.0::gentoo |
94 |
>>> Installing (11 of 20) sys-fs/e2fsprogs-1.46.5-r4::gentoo |
95 |
>>> Emerging (13 of 20) dev-util/meson-1.0.0::gentoo |
96 |
>>> Installing (13 of 20) dev-util/meson-1.0.0::gentoo |
97 |
>>> Emerging (14 of 20) dev-python/cython-0.29.33::gentoo |
98 |
>>> Installing (14 of 20) dev-python/cython-0.29.33::gentoo |
99 |
>>> Emerging (15 of 20) app-misc/pax-utils-1.3.6::gentoo |
100 |
>>> Installing (15 of 20) app-misc/pax-utils-1.3.6::gentoo |
101 |
>>> Emerging (16 of 20) dev-python/pydantic-1.10.4::gentoo |
102 |
>>> Installing (16 of 20) dev-python/pydantic-1.10.4::gentoo |
103 |
>>> Emerging (17 of 20) sys-apps/sandbox-2.30-r1::gentoo |
104 |
>>> Installing (17 of 20) sys-apps/sandbox-2.30-r1::gentoo |
105 |
>>> Failed to execute postinst for sys-apps/sandbox-2.30-r1, Log file: |
106 |
>>> '/var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log' |
107 |
>>> Emerging (18 of 20) sys-apps/portage-3.0.43::gentoo |
108 |
>>> Failed to emerge sys-apps/portage-3.0.43, Log file: |
109 |
>>> '/var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log' |
110 |
* Messages for package sys-apps/portage-3.0.43: |
111 |
* Log file: /var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-050618.log |
112 |
* Unable to find kernel sources at /usr/src/linux |
113 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
114 |
* Messages for package app-alternatives/sh-0: |
115 |
* Log file: /var/tmp/catalyst/log/app-alternatives:sh-0:20230108-053228.log |
116 |
* This package will overwrite one or more files that may belong to other |
117 |
* packages (see list below). |
118 |
* |
119 |
* Detected file collision(s): |
120 |
* |
121 |
* /bin/sh |
122 |
* |
123 |
* Searching all installed packages for file collisions... |
124 |
* |
125 |
* Press Ctrl-C to Stop |
126 |
* |
127 |
* None of the installed packages claim the file(s). |
128 |
* |
129 |
* Package 'app-alternatives/sh-0' merged despite file collisions. If |
130 |
* necessary, refer to your elog messages for the whole content of the |
131 |
* above message. |
132 |
* Messages for package sys-apps/sandbox-2.30-r1: |
133 |
* Log file: /var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log |
134 |
* The ebuild phase 'postinst' has exited unexpectedly. This type of |
135 |
* behavior is known to be triggered by things such as failed variable |
136 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
137 |
* Normally, before exiting, bash should have displayed an error message |
138 |
* above. If bash did not produce an error message above, it's possible |
139 |
* that the ebuild has called `exit` when it should have called `die` |
140 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
141 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
142 |
* not reproducible or it appears to occur randomly, then it is likely to |
143 |
* be triggered by a hardware problem. If you suspect a hardware problem |
144 |
* then you should try some basic hardware diagnostics such as memtest. |
145 |
* Please do not report this as a bug unless it is consistently |
146 |
* reproducible and you are sure that your bash binary and hardware are |
147 |
* functioning properly. |
148 |
* FAILED postinst: 1 |
149 |
* The ebuild phase 'other' has exited unexpectedly. This type of behavior |
150 |
* is known to be triggered by things such as failed variable assignments |
151 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
152 |
* exiting, bash should have displayed an error message above. If bash did |
153 |
* not produce an error message above, it's possible that the ebuild has |
154 |
* called `exit` when it should have called `die` instead. This behavior |
155 |
* may also be triggered by a corrupt bash binary or a hardware problem |
156 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
157 |
* it appears to occur randomly, then it is likely to be triggered by a |
158 |
* hardware problem. If you suspect a hardware problem then you should try |
159 |
* some basic hardware diagnostics such as memtest. Please do not report |
160 |
* this as a bug unless it is consistently reproducible and you are sure |
161 |
* that your bash binary and hardware are functioning properly. |
162 |
* Messages for package sys-apps/portage-3.0.43: |
163 |
* Log file: /var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log |
164 |
* Unable to find kernel sources at /usr/src/linux |
165 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
166 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
167 |
* is known to be triggered by things such as failed variable assignments |
168 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
169 |
* exiting, bash should have displayed an error message above. If bash did |
170 |
* not produce an error message above, it's possible that the ebuild has |
171 |
* called `exit` when it should have called `die` instead. This behavior |
172 |
* may also be triggered by a corrupt bash binary or a hardware problem |
173 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
174 |
* it appears to occur randomly, then it is likely to be triggered by a |
175 |
* hardware problem. If you suspect a hardware problem then you should try |
176 |
* some basic hardware diagnostics such as memtest. Please do not report |
177 |
* this as a bug unless it is consistently reproducible and you are sure |
178 |
* that your bash binary and hardware are functioning properly. |
179 |
|
180 |
|
181 |
|
182 |
|
183 |
|
184 |
|
185 |
|
186 |
|
187 |
* |
188 |
* The following 2 packages have failed to build, install, or execute |
189 |
* postinst: |
190 |
* |
191 |
* (sys-apps/sandbox-2.30-r1:0/0::gentoo, ebuild scheduled for merge) (postinst failed), Log file: |
192 |
* '/var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log' |
193 |
* (sys-apps/portage-3.0.43:0/0::gentoo, ebuild scheduled for merge), Log file: |
194 |
* '/var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log' |
195 |
* |
196 |
08 Jan 2023 06:22:47 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1 |
197 |
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1 |
198 |
08 Jan 2023 06:22:47 UTC: ERROR : Exception running action sequence run_local |
199 |
Traceback (most recent call last): |
200 |
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence |
201 |
func() |
202 |
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 1380, in run_local |
203 |
cmd([self.settings['controller_file'], 'run'], |
204 |
File "/usr/lib/python3.10/site-packages/catalyst/support.py", line 66, in cmd |
205 |
raise CatalystError('cmd(%r) exited %s' % (args, ret), |
206 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1 |
207 |
ERROR:catalyst:Exception running action sequence run_local |
208 |
Traceback (most recent call last): |
209 |
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence |
210 |
func() |
211 |
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 1380, in run_local |
212 |
cmd([self.settings['controller_file'], 'run'], |
213 |
File "/usr/lib/python3.10/site-packages/catalyst/support.py", line 66, in cmd |
214 |
raise CatalystError('cmd(%r) exited %s' % (args, ret), |
215 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1 |
216 |
Command exited with non-zero status 2 |
217 |
10860.36user 513.57system 1:17:22elapsed 245%CPU (0avgtext+0avgdata 530108maxresident)k |
218 |
478792inputs+2144232outputs (394major+216953199minor)pagefaults 0swaps |
219 |
|
220 |
|
221 |
|
222 |
Full build log at /tmp/catalyst-auto.20230106T170214Z.SHiAvp/log/stage1-lp64-musl.log |