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] [x86-auto] Catalyst fatal build error - stage2.spec
Date: Fri, 22 Dec 2017 22:11:37 +0000 (UTC)	[thread overview]
Message-ID: <20171222221137.C04573564F@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] [--versioned-cachedir]
                [--unversioned-cachedir] [-F] [-c CONFIGS] [-f FILE]
                [-s SNAPSHOT] [-C ...]
catalyst: error: argument -f/--file: file does not exist: stage2.spec
Command exited with non-zero status 2
0.12user 0.01system 0:00.19elapsed 70%CPU (0avgtext+0avgdata 63344maxresident)k
328inputs+8outputs (5major+3782minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20171222T214501Z.58gLux/log/stage2.log


             reply	other threads:[~2017-12-22 22:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 22:11 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-15 22:14 [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage2.spec catalyst
2017-12-25 22:12 catalyst
2017-12-20 22:11 catalyst
2017-12-18 23:07 catalyst
2017-12-03 20:35 catalyst
2017-10-26  3:25 catalyst
2015-11-18  4:56 catalyst
2015-11-11  4:52 catalyst
2015-11-04  5:15 catalyst
2015-10-28  4:19 catalyst
2015-08-19  4:13 catalyst
2015-07-22  4:29 catalyst
2015-04-08  4:26 catalyst
2015-03-04  5:02 catalyst
2014-12-31  5:46 catalyst
2014-12-17  5:15 catalyst
2014-11-12  5:15 catalyst
2011-09-06  5:03 catalyst
2011-03-29  4:29 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=20171222221137.C04573564F@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