public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@demeter.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst build success
Date: Sun,  4 Jun 2023 09:04:45 +0000 (UTC)	[thread overview]
Message-ID: <20230604090445.D6822268042@demeter.amd64.dev.gentoo.org> (raw)

Build process complete.


*** Running command: post_build openrc stage1-openrc.spec
Finished stage1-openrc.spec
*** Running command: post_build openrc stage3-openrc.spec
Uploading stage3-m68k-openrc-20230531T170205Z.tar.xz stage3-m68k-openrc-20230531T170205Z.tar.xz.CONTENTS.gz stage3-m68k-openrc-20230531T170205Z.tar.xz.DIGESTS stage3-m68k-openrc-20230531T170205Z.tar.xz.sha256
*** Running command: post_build systemd stage1-systemd.spec
Finished stage1-systemd.spec
*** Running command: post_build systemd stage3-systemd.spec
Uploading stage3-m68k-systemd-20230531T170205Z.tar.xz stage3-m68k-systemd-20230531T170205Z.tar.xz.CONTENTS.gz stage3-m68k-systemd-20230531T170205Z.tar.xz.DIGESTS stage3-m68k-systemd-20230531T170205Z.tar.xz.sha256
*** Running command: post_build systemd_mu stage1-systemd-mu.spec
Finished stage1-systemd-mu.spec
*** Running command: post_build systemd_mu stage3-systemd-mu.spec
Uploading stage3-m68k-systemd-mergedusr-20230531T170205Z.tar.xz stage3-m68k-systemd-mergedusr-20230531T170205Z.tar.xz.CONTENTS.gz stage3-m68k-systemd-mergedusr-20230531T170205Z.tar.xz.DIGESTS stage3-m68k-systemd-mergedusr-20230531T170205Z.tar.xz.sha256
*** Running command: post_build  
Finished 



Full build log at /tmp/catalyst-auto.20230531T170205Z.oBJKXK/log/post_build.log


             reply	other threads:[~2023-06-04  9:04 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04  9:04 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-14 12:36 [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst build success catalyst
2023-12-08  6:59 catalyst
2023-10-26 21:14 catalyst
2023-10-21  8:21 catalyst
2023-10-05 20:51 catalyst
2023-09-28 15:53 catalyst
2023-09-22  1:27 catalyst
2023-09-14 17:34 catalyst
2023-09-07 18:46 catalyst
2023-09-03  9:11 catalyst
2023-08-24 15:25 catalyst
2023-08-18  1:52 catalyst
2023-08-16  0:32 catalyst
2023-07-27  8:15 catalyst
2023-07-25  1:18 catalyst
2023-07-20 16:06 catalyst
2023-07-13 14:56 catalyst
2023-06-29 17:22 catalyst
2023-06-22 12:14 catalyst
2023-06-15  6:14 catalyst
2023-06-08 10:45 catalyst
2023-05-27 11:10 catalyst
2023-05-18  7:43 catalyst
2023-05-11  9:35 catalyst
2023-05-05  3:54 catalyst
2023-04-29  0:06 catalyst
2023-04-20 13:53 catalyst
2023-04-13  8:45 catalyst
2023-04-06 15:19 catalyst
2023-03-30 17:22 catalyst
2023-03-23 19:07 catalyst
2023-03-10 20:00 catalyst
2023-03-02 11:11 catalyst
2023-02-23 12:41 catalyst
2023-02-16 15:10 catalyst
2023-02-09 13:44 catalyst
2023-02-02 15:06 catalyst
2023-01-30  6:16 catalyst
2023-01-12 16:51 catalyst
2023-01-06 23:38 catalyst
2022-12-30 17:58 catalyst
2022-12-25 18:49 catalyst
2022-12-11  3:37 catalyst
2022-12-03 16:33 catalyst
2022-11-24 14:09 catalyst
2022-11-17  3:44 catalyst
2022-11-10  6:29 catalyst
2022-11-03 13:26 catalyst
2022-10-27 10:08 catalyst
2022-10-22  1:17 catalyst
2022-10-13 14:10 catalyst
2022-10-06  2:25 catalyst
2022-09-29  3:21 catalyst
2022-09-22  4:34 catalyst
2022-09-15 11:21 catalyst
2022-09-08  3:02 catalyst
2022-09-07 13:25 catalyst
2022-06-02  0:20 catalyst
2022-06-01  6:32 catalyst
2022-05-30  7:00 catalyst
2021-11-10 22:46 catalyst
2021-10-27 23:12 catalyst
2021-10-20 19:34 catalyst
2021-10-13 21:18 catalyst
2021-10-06 20:29 catalyst
2021-09-29 21:13 catalyst
2021-09-22 20:07 catalyst
2021-09-15 19:55 catalyst
2021-09-08 21:17 catalyst
2021-09-02 19:08 catalyst
2021-08-30  9:25 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=20230604090445.D6822268042@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