From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
Date: Mon, 15 Jun 2020 03:00:25 +0000 (UTC) [thread overview]
Message-ID: <20200807022901.2491E60558@thor.jmbsvicetto.name> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f stage4-nomultilib-minimal.spec
15 Jun 2020 03:00:25 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
15 Jun 2020 03:00:25 UTC: NOTICE : conf_values[options] = {'bindist', 'clear-autoresume', 'preserve_libs', 'pkgcache'}
15 Jun 2020 03:00:25 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
15 Jun 2020 03:00:25 UTC: NOTICE : Using target: stage4
15 Jun 2020 03:00:25 UTC: NOTICE : Source file specification matching setting is: loose
15 Jun 2020 03:00:25 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
15 Jun 2020 03:00:25 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
15 Jun 2020 03:00:25 UTC: ERROR : CatalystError: Cannot locate specified distdir: /usr/portage/distfiles
Command exited with non-zero status 2
0.70user 0.02system 0:00.78elapsed 93%CPU (0avgtext+0avgdata 17060maxresident)k
0inputs+0outputs (0major+8950minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20200615T030003Z.L43AzO/log/stage4-nomultilib-minimal.log
next reply other threads:[~2020-09-30 18:30 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 3:00 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-28 3:00 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec catalyst
2020-09-21 3:00 catalyst
2020-09-14 3:00 catalyst
2020-09-07 3:00 catalyst
2020-08-31 3:00 catalyst
2020-08-24 3:00 catalyst
2020-08-17 3:00 catalyst
2020-08-10 3:02 catalyst
2020-08-03 3:00 catalyst
2020-07-27 3:00 catalyst
2020-07-20 3:00 catalyst
2020-07-13 3:00 catalyst
2020-07-06 3:00 catalyst
2020-06-29 16:21 catalyst
2020-06-29 3:00 catalyst
2020-06-29 0:00 catalyst
2020-06-22 3:00 catalyst
2020-06-17 22:35 catalyst
2020-06-14 22:37 catalyst
2020-06-08 3:00 catalyst
2020-06-01 3:00 catalyst
2020-05-25 3:00 catalyst
2020-05-18 3:00 catalyst
2020-05-12 3:38 catalyst
2020-05-11 16:26 catalyst
2020-05-11 11:32 catalyst
2020-05-11 3:01 catalyst
2020-05-04 3:12 catalyst
2020-04-27 3:00 catalyst
2020-04-13 4:01 catalyst
2020-04-06 3:58 catalyst
2020-03-30 3:59 catalyst
2020-03-23 3:57 catalyst
2020-03-16 3:56 catalyst
2020-03-09 3:57 catalyst
2020-03-02 3:54 catalyst
2020-02-24 3:44 catalyst
2020-02-17 3:42 catalyst
2020-02-10 3:37 catalyst
2020-02-03 3:38 catalyst
2020-01-27 3:38 catalyst
2020-01-20 3:39 catalyst
2020-01-13 3:40 catalyst
2019-12-09 1:06 catalyst
2019-07-16 3:06 catalyst
2019-07-16 3:00 catalyst
2019-07-16 2:55 catalyst
2019-07-16 2:51 catalyst
2019-05-31 11:23 catalyst
2019-05-30 6:00 catalyst
2019-05-29 14:35 catalyst
2019-05-27 8:07 catalyst
2018-08-14 16:27 catalyst
2018-08-11 9:51 catalyst
2018-08-11 9:48 catalyst
2018-07-16 22:32 catalyst
2018-07-16 16:13 catalyst
2018-07-04 5:06 catalyst
2018-07-02 7:47 catalyst
2018-06-28 3:12 catalyst
2018-06-25 8:57 catalyst
2018-06-25 7:00 catalyst
2018-06-18 4:22 catalyst
2018-06-15 22:16 catalyst
2018-05-30 2:37 catalyst
2018-02-21 0:01 catalyst
2018-02-03 15:59 catalyst
2018-02-01 23:02 catalyst
2018-02-01 0:52 catalyst
2018-01-07 14:15 catalyst
2018-01-05 4:19 catalyst
2018-01-04 9:17 catalyst
2017-12-31 11:51 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23 3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15 7:26 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=20200807022901.2491E60558@thor.jmbsvicetto.name \
--to=catalyst@thor.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/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