From: catalyst@milou.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst fatal build error - stage1-openrc-23.spec
Date: Wed, 3 Jul 2024 17:11:46 +0000 (UTC) [thread overview]
Message-ID: <20240703171146.3438D7482F6@milou.amd64.dev.gentoo.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 9275 bytes --]
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20240703T164902Z.Uf1u5n/specs/stage1-openrc-23.spec
03 Jul 2024 17:05:10 UTC: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
03 Jul 2024 17:05:10 UTC: NOTICE : conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache', 'clear-autoresume']
03 Jul 2024 17:05:10 UTC: NOTICE : Processing spec file: /tmp/catalyst-auto.20240703T164902Z.Uf1u5n/specs/stage1-openrc-23.spec
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20240703T164902Z.Uf1u5n/specs/stage1-openrc-23.spec
03 Jul 2024 17:05:10 UTC: NOTICE : Using target: stage1
NOTICE:catalyst:Using target: stage1
03 Jul 2024 17:05:10 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
NOTICE:catalyst:Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
03 Jul 2024 17:05:10 UTC: NOTICE : Source path set to /var/tmp/catalyst/builds/23.0-default/stage3-m68k-openrc-latest.tar.xz
NOTICE:catalyst:Source path set to /var/tmp/catalyst/builds/23.0-default/stage3-m68k-openrc-latest.tar.xz
03 Jul 2024 17:05:10 UTC: NOTICE : --- Running action sequence: unpack
NOTICE:catalyst:--- Running action sequence: unpack
03 Jul 2024 17:05:10 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
NOTICE:catalyst:Referenced SEEDCACHE does not appear to be a directory, trying to untar...
03 Jul 2024 17:05:10 UTC: NOTICE : Clearing the chroot path ...
NOTICE:catalyst:Clearing the chroot path ...
03 Jul 2024 17:05:10 UTC: NOTICE : Starting auto from /var/tmp/catalyst/builds/23.0-default/stage3-m68k-openrc-latest.tar.xz
NOTICE:catalyst:Starting auto from /var/tmp/catalyst/builds/23.0-default/stage3-m68k-openrc-latest.tar.xz
03 Jul 2024 17:05:10 UTC: NOTICE : to /var/tmp/catalyst/tmp/23.0-default/stage1-m68k-openrc-20240703T164902Z (this may take some time) ..
NOTICE:catalyst:to /var/tmp/catalyst/tmp/23.0-default/stage1-m68k-openrc-20240703T164902Z (this may take some time) ..
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: config_profile_link
NOTICE:catalyst:--- Running action sequence: config_profile_link
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: setup_confdir
NOTICE:catalyst:--- Running action sequence: setup_confdir
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: process_repos
NOTICE:catalyst:--- Running action sequence: process_repos
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: bind
NOTICE:catalyst:--- Running action sequence: bind
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: chroot_setup
NOTICE:catalyst:--- Running action sequence: chroot_setup
03 Jul 2024 17:05:12 UTC: NOTICE : Setting up chroot...
NOTICE:catalyst:Setting up chroot...
03 Jul 2024 17:05:12 UTC: NOTICE : Copying binary interpreter /usr/bin/qemu-m68k into chroot
NOTICE:catalyst:Copying binary interpreter /usr/bin/qemu-m68k into chroot
03 Jul 2024 17:05:12 UTC: WARNING : env variables in catalystrc may cause catastrophic failure.
WARNING:catalyst:env variables in catalystrc may cause catastrophic failure.
03 Jul 2024 17:05:12 UTC: WARNING : If your build fails look here first as the possible problem.
WARNING:catalyst:If your build fails look here first as the possible problem.
03 Jul 2024 17:05:12 UTC: NOTICE : Writing the stage make.conf to: /var/tmp/catalyst/tmp/23.0-default/stage1-m68k-openrc-20240703T164902Z/etc/portage/make.conf
NOTICE:catalyst:Writing the stage make.conf to: /var/tmp/catalyst/tmp/23.0-default/stage1-m68k-openrc-20240703T164902Z/etc/portage/make.conf
03 Jul 2024 17:05:12 UTC: NOTICE : STICKY-CONFIG is enabled
NOTICE:catalyst:STICKY-CONFIG is enabled
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: setup_environment
NOTICE:catalyst:--- Running action sequence: setup_environment
03 Jul 2024 17:05:12 UTC: NOTICE : --- Running action sequence: run_local
NOTICE:catalyst:--- Running action sequence: run_local
Running chroot.sh in chroot:
chroot /var/tmp/catalyst/tmp/23.0-default/stage1-m68k-openrc-20240703T164902Z /tmp/chroot.sh
>>> Regenerating /etc/ld.so.cache...
Updating seed stage...
emerge --quiet --jobs 10 --load-average 64.0 --buildpkg=n -uDN @world
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-lang/python-3.12.4_p2
>>> Running pre-merge checks for net-misc/openssh-9.8_p1-r1
>>> Emerging (1 of 15) sec-keys/openpgp-keys-gentoo-release-20240703::gentoo
>>> Emerging (2 of 15) dev-python/ensurepip-pip-24.1.1::gentoo
>>> Emerging (3 of 15) app-shells/bash-5.2_p26-r6::gentoo
>>> Failed to emerge sec-keys/openpgp-keys-gentoo-release-20240703, Log file:
>>> '/var/log/portage/sec-keys:openpgp-keys-gentoo-release-20240703:20240703-170609.log'
>>> Installing (2 of 15) dev-python/ensurepip-pip-24.1.1::gentoo
>>> Completed (2 of 15) dev-python/ensurepip-pip-24.1.1::gentoo
>>> Installing (3 of 15) app-shells/bash-5.2_p26-r6::gentoo
>>> Completed (3 of 15) app-shells/bash-5.2_p26-r6::gentoo
--2024-07-03 17:06:10-- http://distfiles.gentoo.org/distfiles/27/gentoo-release.asc.20240703.gz
Resolving distfiles.gentoo.org... 2a02:6ea0:c500::4, 2a02:6ea0:c500::3, 185.76.9.26, ...
Connecting to distfiles.gentoo.org|2a02:6ea0:c500::4|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-07-03 17:06:10 ERROR 404: Not Found.
--2024-07-03 17:06:10-- https://dev.gentoo.org/~mgorny/dist/openpgp-keys/gentoo-release.asc.20240703.gz
Resolving dev.gentoo.org... 2001:470:ea4a:1:5054:ff:fec7:86e4, 140.211.166.183
Connecting to dev.gentoo.org|2001:470:ea4a:1:5054:ff:fec7:86e4|:443... connected.
ERROR: cannot verify dev.gentoo.org's certificate, issued by ‘CN=R3,O=Let's Encrypt,C=US’:
Unable to locally verify the issuer's authority.
To connect to dev.gentoo.org insecurely, use `--no-check-certificate'.
!!! Couldn't download 'gentoo-release.asc.20240703.gz'. Aborting.
* Messages for package app-shells/bash-5.2_p26-r6:
* Log file: /var/log/portage/app-shells:bash-5.2_p26-r6:20240703-170610.log
* Files situated under /etc/bash/bashrc.d must now have a suffix of .sh or .bash.
*
* Gentoo now defaults to defining PROMPT_COMMAND as an array. Depending on the
* characteristics of the operating environment, this array may contain a command
* to set the terminal's window title. Those already choosing to customise the
* PROMPT_COMMAND variable are now advised to append their commands like so:
*
* PROMPT_COMMAND+=('custom command goes here')
*
* Gentoo no longer defaults to having bash manipulate the window title in the case
* that the terminal is controlled by sshd(8), unless screen or tmux are in use.
* Those wanting to set the title unconditionally may adjust ~/.bashrc - or create
* a custom /etc/bash/bashrc.d drop-in - to set PROMPT_COMMMAND like so:
*
* PROMPT_COMMAND=(genfun_set_win_title)
*
* Those who would prefer for bash never to interfere with the window title may
* now opt out of the default title setting behaviour, either with the "unset -v
* PROMPT_COMMAND" command or by re-defining PROMPT_COMMAND as desired.
03 Jul 2024 17:11:46 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
03 Jul 2024 17:11:46 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
func()
File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 1441, in run_local
cmd([self.settings['controller_file'], 'run'],
File "/usr/lib/python3.12/site-packages/catalyst/support.py", line 66, in cmd
raise CatalystError('cmd(%r) exited %s' % (args, ret),
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
ERROR:catalyst:Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
func()
File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 1441, in run_local
cmd([self.settings['controller_file'], 'run'],
File "/usr/lib/python3.12/site-packages/catalyst/support.py", line 66, in cmd
raise CatalystError('cmd(%r) exited %s' % (args, ret),
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
Command exited with non-zero status 2
743.19user 42.44system 6:35.87elapsed 198%CPU (0avgtext+0avgdata 1142528maxresident)k
411256inputs+2125608outputs (53major+13659978minor)pagefaults 0swaps
Full build log at /tmp/catalyst-auto.20240703T164902Z.Uf1u5n/log/stage1-openrc-23.log
next reply other threads:[~2024-07-03 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 17:11 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 18:53 [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst fatal build error - stage1-openrc-23.spec catalyst
2024-08-28 17:05 catalyst
2024-06-19 23:12 catalyst
2024-06-12 0:49 catalyst
2024-06-05 21:21 catalyst
2024-05-29 19:00 catalyst
2024-05-22 19:54 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240703171146.3438D7482F6@milou.amd64.dev.gentoo.org \
--to=catalyst@milou.amd64.dev.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox