public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@hake.hppa.dev.gentoo.org
To: gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa2.0/stage1-systemd-23.spec
Date: Sun, 13 Apr 2025 12:26:53 -0400	[thread overview]
Message-ID: <20250413162654.130201104B0@bobolink.gentoo.org> (raw)




*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /usr/local/catalyst/tmp/catalyst-auto.20250410T070518Z.vn7QIA/specs/hppa2.0/stage1-systemd-23.spec
13 Apr 2025 09:52:10 EDT: NOTICE  : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
13 Apr 2025 09:52:10 EDT: NOTICE  : conf_values[options] = ['autoresume', 'bindist', 'kerncache', 'pkgcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['autoresume', 'bindist', 'kerncache', 'pkgcache', 'clear-autoresume']
13 Apr 2025 09:52:10 EDT: NOTICE  : Processing spec file: /usr/local/catalyst/tmp/catalyst-auto.20250410T070518Z.vn7QIA/specs/hppa2.0/stage1-systemd-23.spec
NOTICE:catalyst:Processing spec file: /usr/local/catalyst/tmp/catalyst-auto.20250410T070518Z.vn7QIA/specs/hppa2.0/stage1-systemd-23.spec
13 Apr 2025 09:52:11 EDT: NOTICE  : Using target: stage1
NOTICE:catalyst:Using target: stage1
13 Apr 2025 09:52:11 EDT: NOTICE  : Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2']
NOTICE:catalyst:Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2']
13 Apr 2025 09:52:32 EDT: NOTICE  : Source path set to /usr/local/catalyst/builds/23.0-default/stage3-hppa2.0-systemd-latest.tar.xz
NOTICE:catalyst:Source path set to /usr/local/catalyst/builds/23.0-default/stage3-hppa2.0-systemd-latest.tar.xz
13 Apr 2025 09:52:33 EDT: NOTICE  : Removing AutoResume Points ...
NOTICE:catalyst:Removing AutoResume Points ...
13 Apr 2025 09:52:33 EDT: NOTICE  : Emptying directory: /usr/local/catalyst/tmp/23.0-default/.autoresume-stage1-hppa2.0-systemd-20250410T070518Z
NOTICE:catalyst:Emptying directory: /usr/local/catalyst/tmp/23.0-default/.autoresume-stage1-hppa2.0-systemd-20250410T070518Z
13 Apr 2025 09:52:33 EDT: NOTICE  : --- Running action sequence: unpack
NOTICE:catalyst:--- Running action sequence: unpack
13 Apr 2025 09:52:33 EDT: NOTICE  : Resume: Target chroot is invalid, cleaning up...
NOTICE:catalyst:Resume: Target chroot is invalid, cleaning up...
13 Apr 2025 09:52:33 EDT: NOTICE  : Removing AutoResume Points ...
NOTICE:catalyst:Removing AutoResume Points ...
13 Apr 2025 09:52:33 EDT: NOTICE  : Emptying directory: /usr/local/catalyst/tmp/23.0-default/.autoresume-stage1-hppa2.0-systemd-20250410T070518Z
NOTICE:catalyst:Emptying directory: /usr/local/catalyst/tmp/23.0-default/.autoresume-stage1-hppa2.0-systemd-20250410T070518Z
13 Apr 2025 09:52:33 EDT: NOTICE  : Clearing the chroot path ...
NOTICE:catalyst:Clearing the chroot path ...
13 Apr 2025 09:52:33 EDT: NOTICE  : Starting auto from /usr/local/catalyst/builds/23.0-default/stage3-hppa2.0-systemd-latest.tar.xz
NOTICE:catalyst:Starting auto from /usr/local/catalyst/builds/23.0-default/stage3-hppa2.0-systemd-latest.tar.xz
13 Apr 2025 09:52:33 EDT: NOTICE  : to /usr/local/catalyst/tmp/23.0-default/stage1-hppa2.0-systemd-20250410T070518Z (this may take some time) ..
NOTICE:catalyst:to /usr/local/catalyst/tmp/23.0-default/stage1-hppa2.0-systemd-20250410T070518Z (this may take some time) ..
13 Apr 2025 09:58:52 EDT: NOTICE  : --- Running action sequence: config_profile_link
NOTICE:catalyst:--- Running action sequence: config_profile_link
13 Apr 2025 09:58:52 EDT: NOTICE  : --- Running action sequence: setup_confdir
NOTICE:catalyst:--- Running action sequence: setup_confdir
13 Apr 2025 09:58:57 EDT: NOTICE  : --- Running action sequence: process_repos
NOTICE:catalyst:--- Running action sequence: process_repos
13 Apr 2025 09:58:58 EDT: NOTICE  : --- Running action sequence: bind
NOTICE:catalyst:--- Running action sequence: bind
13 Apr 2025 09:58:58 EDT: NOTICE  : --- Running action sequence: chroot_setup
NOTICE:catalyst:--- Running action sequence: chroot_setup
13 Apr 2025 09:58:58 EDT: NOTICE  : Setting up chroot...
NOTICE:catalyst:Setting up chroot...
13 Apr 2025 09:58:58 EDT: WARNING : env variables in catalystrc may cause catastrophic failure.
WARNING:catalyst:env variables in catalystrc may cause catastrophic failure.
13 Apr 2025 09:58:58 EDT: 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.
13 Apr 2025 09:58:58 EDT: NOTICE  : Writing the stage make.conf to: /usr/local/catalyst/tmp/23.0-default/stage1-hppa2.0-systemd-20250410T070518Z/etc/portage/make.conf
NOTICE:catalyst:Writing the stage make.conf to: /usr/local/catalyst/tmp/23.0-default/stage1-hppa2.0-systemd-20250410T070518Z/etc/portage/make.conf
13 Apr 2025 09:58:58 EDT: NOTICE  : STICKY-CONFIG is enabled
NOTICE:catalyst:STICKY-CONFIG is enabled
13 Apr 2025 09:58:58 EDT: NOTICE  : --- Running action sequence: setup_environment
NOTICE:catalyst:--- Running action sequence: setup_environment
13 Apr 2025 09:58:58 EDT: NOTICE  : --- Running action sequence: run_local
NOTICE:catalyst:--- Running action sequence: run_local
Running chroot.sh in chroot:
    chroot /usr/local/catalyst/tmp/23.0-default/stage1-hppa2.0-systemd-20250410T070518Z /tmp/chroot.sh
>>> Regenerating /etc/ld.so.cache...
Updating seed stage...
emerge --quiet --buildpkg=n --update --deep --newuse @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 sys-apps/systemd-256.10
 ^[[32m*^[[0m Determining the location of the kernel source code
 ^[[33;01m*^[[0m Unable to find kernel sources at /usr/src/linux
 ^[[32m*^[[0m Please make sure that /usr/src/linux points at your running kernel, 
 ^[[32m*^[[0m (or the kernel you wish to build against).
 ^[[32m*^[[0m Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
 ^[[33;01m*^[[0m Unable to calculate Linux Kernel version for build, attempting to use running version
 ^[[33;01m*^[[0m Unable to check for the following kernel config options due
 ^[[33;01m*^[[0m to absence of any configured kernel sources or compiled
 ^[[33;01m*^[[0m config:
 ^[[33;01m*^[[0m  - BLK_DEV_BSG
 ^[[33;01m*^[[0m  - CGROUPS
 ^[[33;01m*^[[0m  - CGROUP_BPF
 ^[[33;01m*^[[0m  - DEVTMPFS
 ^[[33;01m*^[[0m  - EPOLL
 ^[[33;01m*^[[0m  - FANOTIFY
 ^[[33;01m*^[[0m  - FHANDLE
 ^[[33;01m*^[[0m  - INOTIFY_USER
 ^[[33;01m*^[[0m  - IPV6
 ^[[33;01m*^[[0m  - NET
 ^[[33;01m*^[[0m  - NET_NS
 ^[[33;01m*^[[0m  - PROC_FS
 ^[[33;01m*^[[0m  - SIGNALFD
 ^[[33;01m*^[[0m  - SYSFS
 ^[[33;01m*^[[0m  - TIMERFD
 ^[[33;01m*^[[0m  - TMPFS_XATTR
 ^[[33;01m*^[[0m  - UNIX
 ^[[33;01m*^[[0m  - USER_NS
 ^[[33;01m*^[[0m  - CRYPTO_HMAC
 ^[[33;01m*^[[0m  - CRYPTO_SHA256
 ^[[33;01m*^[[0m  - CRYPTO_USER_API_HASH
 ^[[33;01m*^[[0m  - GRKERNSEC_PROC
 ^[[33;01m*^[[0m  - IDE
 ^[[33;01m*^[[0m  - SYSFS_DEPRECATED
 ^[[33;01m*^[[0m  - SYSFS_DEPRECATED_V2
 ^[[33;01m*^[[0m  - TMPFS_POSIX_ACL
 ^[[33;01m*^[[0m  - SECCOMP
 ^[[33;01m*^[[0m  - SECCOMP_FILTER
 ^[[33;01m*^[[0m  - KCMP
 ^[[33;01m*^[[0m  - AUTOFS_FS
 ^[[33;01m*^[[0m You're on your own to make sure they are set if needed.
>>> Running pre-merge checks for sys-apps/portage-3.0.67
 ^[[32m*^[[0m Determining the location of the kernel source code
 ^[[33;01m*^[[0m Unable to find kernel sources at /usr/src/linux
 ^[[32m*^[[0m Please make sure that /usr/src/linux points at your running kernel, 
 ^[[32m*^[[0m (or the kernel you wish to build against).
 ^[[32m*^[[0m Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
 ^[[33;01m*^[[0m Unable to calculate Linux Kernel version for build, attempting to use running version
 ^[[33;01m*^[[0m Unable to check for the following kernel config options due
 ^[[33;01m*^[[0m to absence of any configured kernel sources or compiled
 ^[[33;01m*^[[0m config:
 ^[[33;01m*^[[0m  - IPC_NS
 ^[[33;01m*^[[0m  - PID_NS
 ^[[33;01m*^[[0m  - NET_NS
 ^[[33;01m*^[[0m  - UTS_NS
 ^[[33;01m*^[[0m You're on your own to make sure they are set if needed.
>>> Running pre-merge checks for net-misc/openssh-9.9_p2
>>> Emerging (1 of 30) sys-libs/ncurses-6.5_p20250125::gentoo
[ERROR] Exception in callback PipeLogger._io_loop_done(<Task finishe...t on device')>)
handle: <Handle PipeLogger._io_loop_done(<Task finishe...t on device')>)>
Traceback (most recent call last):
  File "/usr/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args


Full build log at /var/tmp/catalyst/tmp/catalyst-auto.20250410T070518Z.vn7QIA/log/hppa2.0_stage1-systemd-23.log


             reply	other threads:[~2025-04-13 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-13 16:26 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-06 19:10 [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa2.0/stage1-systemd-23.spec catalyst
2025-04-02  8:01 catalyst
2025-03-09 14:53 catalyst
2025-02-27 23:04 catalyst
2025-02-20 10:02 catalyst
2024-12-04 16:20 catalyst
2024-12-02 20:38 catalyst
2024-11-20  3:51 catalyst
2024-11-17 10:04 catalyst
2024-08-10  3:07 catalyst
2024-08-07  4:37 catalyst
2024-07-07 18:39 catalyst
2024-07-01  4:14 catalyst
2024-06-23 10:43 catalyst
2024-06-18  6:51 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=20250413162654.130201104B0@bobolink.gentoo.org \
    --to=catalyst@hake.hppa.dev.gentoo.org \
    --cc=gentoo-releng-autobuilds@lists.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