From: catalyst@demeter.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [aarch64_be-auto] Catalyst build success
Date: Sun, 19 Mar 2023 04:59:35 +0000 (UTC) [thread overview]
Message-ID: <20230319045935.8876F268042@demeter.amd64.dev.gentoo.org> (raw)
Build process complete.
*** Running command: post_build openrc stage1-openrc.spec
*** Running command: post_build openrc stage3-openrc.spec
Uploading stage3-aarch64_be-openrc-20230318T170216Z.tar.xz stage3-aarch64_be-openrc-20230318T170216Z.tar.xz.CONTENTS.gz stage3-aarch64_be-openrc-20230318T170216Z.tar.xz.DIGESTS stage3-aarch64_be-openrc-20230318T170216Z.tar.xz.sha256
*** Running command: post_build systemd stage1-systemd.spec
*** Running command: post_build systemd stage3-systemd.spec
Uploading stage3-aarch64_be-systemd-20230318T170216Z.tar.xz stage3-aarch64_be-systemd-20230318T170216Z.tar.xz.CONTENTS.gz stage3-aarch64_be-systemd-20230318T170216Z.tar.xz.DIGESTS stage3-aarch64_be-systemd-20230318T170216Z.tar.xz.sha256
*** Running command: post_build systemd_mu stage1-systemd-mu.spec
*** Running command: post_build systemd_mu stage3-systemd-mu.spec
Uploading stage3-aarch64_be-systemd-mergedusr-20230318T170216Z.tar.xz stage3-aarch64_be-systemd-mergedusr-20230318T170216Z.tar.xz.CONTENTS.gz stage3-aarch64_be-systemd-mergedusr-20230318T170216Z.tar.xz.DIGESTS stage3-aarch64_be-systemd-mergedusr-20230318T170216Z.tar.xz.sha256
*** Running command: post_build
Full build log at /tmp/catalyst-auto.20230318T170216Z.c7DHrD/log/post_build.log
next reply other threads:[~2023-03-19 4:59 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 4:59 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-13 7:54 [gentoo-releng-autobuilds] [aarch64_be-auto] Catalyst build success catalyst
2024-10-06 0:21 catalyst
2024-09-29 2:39 catalyst
2024-09-22 2:04 catalyst
2024-09-08 1:39 catalyst
2024-08-31 23:51 catalyst
2024-08-24 23:46 catalyst
2024-08-17 22:52 catalyst
2024-08-10 23:48 catalyst
2024-08-04 0:30 catalyst
2024-07-28 0:08 catalyst
2024-07-21 10:53 catalyst
2024-07-14 0:51 catalyst
2024-07-07 2:33 catalyst
2024-06-30 3:29 catalyst
2024-06-23 0:58 catalyst
2024-06-16 0:02 catalyst
2024-06-09 5:20 catalyst
2024-06-02 1:02 catalyst
2024-05-26 9:53 catalyst
2024-05-19 1:45 catalyst
2024-05-12 7:07 catalyst
2024-05-05 20:23 catalyst
2024-04-28 7:19 catalyst
2024-04-21 11:41 catalyst
2024-04-14 7:59 catalyst
2024-04-07 7:18 catalyst
2024-03-31 18:00 catalyst
2024-03-24 21:51 catalyst
2024-03-18 16:21 catalyst
2024-03-11 10:37 catalyst
2024-02-26 1:50 catalyst
2024-02-18 9:50 catalyst
2024-02-17 6:44 catalyst
2024-02-16 0:03 catalyst
2024-02-11 9:24 catalyst
2024-02-04 22:56 catalyst
2024-01-30 21:29 catalyst
2024-01-22 19:54 catalyst
2024-01-18 10:33 catalyst
2024-01-09 8:07 catalyst
2023-12-25 22:04 catalyst
2023-12-18 22:22 catalyst
2023-12-10 6:51 catalyst
2023-12-03 4:21 catalyst
2023-11-26 3:17 catalyst
2023-11-19 8:17 catalyst
2023-11-12 6:45 catalyst
2023-11-05 7:00 catalyst
2023-10-29 4:07 catalyst
2023-10-22 13:23 catalyst
2023-10-15 8:27 catalyst
2023-10-09 17:24 catalyst
2023-09-17 4:10 catalyst
2023-09-10 4:26 catalyst
2023-09-03 17:39 catalyst
2023-08-27 4:40 catalyst
2023-08-20 9:00 catalyst
2023-08-06 4:09 catalyst
2023-07-30 10:14 catalyst
2023-07-23 7:19 catalyst
2023-07-16 12:04 catalyst
2023-07-10 5:09 catalyst
2023-06-25 12:40 catalyst
2023-06-18 3:50 catalyst
2023-06-11 3:59 catalyst
2023-06-04 23:19 catalyst
2023-05-28 9:33 catalyst
2023-05-21 3:28 catalyst
2023-05-14 4:29 catalyst
2023-05-07 12:38 catalyst
2023-05-03 2:17 catalyst
2023-04-23 2:02 catalyst
2023-04-16 2:58 catalyst
2023-04-09 6:30 catalyst
2023-04-02 1:30 catalyst
2023-03-26 8:29 catalyst
2023-03-12 11:48 catalyst
2023-03-05 10:06 catalyst
2023-02-26 8:15 catalyst
2023-02-12 4:25 catalyst
2023-02-05 7:28 catalyst
2023-02-01 1:04 catalyst
2023-01-22 3:59 catalyst
2023-01-21 2:33 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=20230319045935.8876F268042@demeter.amd64.dev.gentoo.org \
--to=catalyst@demeter.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