public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage4-cloud.spec
Date: Sun,  3 Dec 2017 20:46:56 +0000 (UTC)	[thread overview]
Message-ID: <20171203204656.64718353A0@nightheron.gentoo.org> (raw)




usage: catalyst [-h] [-V] [-d] [-v]
                [--log-level {critical,error,warning,notice,info,debug}]
                [--log-file LOG_FILE] [--color] [--nocolor] [--trace]
                [--profile] [-a] [-p] [-P] [-T] [-F] [-c CONFIGS] [-f FILE]
                [-s SNAPSHOT] [-C ...]
catalyst: error: argument -f/--file: file does not exist: stage4-cloud.spec
Command exited with non-zero status 2
0.13user 0.00system 0:00.14elapsed 99%CPU (0avgtext+0avgdata 62720maxresident)k
0inputs+8outputs (0major+3819minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20171203.SmV1sP/log/stage4-cloud.log


             reply	other threads:[~2017-12-03 20:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 20:46 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-03 21:10 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage4-cloud.spec catalyst
2017-12-03 20:40 catalyst
2017-11-30  6:36 catalyst
2017-11-23  7:26 catalyst
2017-11-16  6:32 catalyst
2017-11-09  6:18 catalyst
2017-11-02  6:22 catalyst
2017-10-26  6:14 catalyst
2017-10-19  6:16 catalyst
2017-10-12  6:14 catalyst
2017-10-05  6:23 catalyst
2017-03-01  3:47 catalyst
2016-07-30 12:58 catalyst
2016-07-25  3:01 catalyst
2016-05-30  3:00 catalyst
2016-04-30 13:17 catalyst
2016-04-28  7:33 catalyst
2016-01-25  9:12 catalyst
2015-12-28  4:19 catalyst
2015-12-28  3:00 catalyst
2015-12-21  2:34 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=20171203204656.64718353A0@nightheron.gentoo.org \
    --to=catalyst@nightheron.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