From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-cloud.spec
Date: Mon, 28 Dec 2015 04:19:08 +0000 (UTC) [thread overview]
Message-ID: <20151228041908.3B3DEE006E@lantean.jmbsvicetto.name> (raw)
28 Dec 2015 04:19:07 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
28 Dec 2015 04:19:07 UTC: NOTICE : Using target: stage4
28 Dec 2015 04:19:08 UTC: ERROR : CatalystError: Ambiguos Filename: /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest
28 Dec 2015 04:19:08 UTC: ERROR : Please specify the correct extension as well
Full build log at /home/release/tmp/run/catalyst-auto.cG2nDx/log/hardened_stage4-cloud.log
next reply other threads:[~2015-12-28 4:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 4:19 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-03 21:11 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-cloud.spec catalyst
2017-12-03 20:47 catalyst
2017-12-03 20:41 catalyst
2017-12-01 0:31 catalyst
2017-11-24 3:47 catalyst
2017-11-16 23:59 catalyst
2017-11-09 23:14 catalyst
2017-11-02 23:42 catalyst
2017-10-26 22:59 catalyst
2017-10-19 22:53 catalyst
2017-10-12 22:41 catalyst
2017-10-05 23:18 catalyst
2017-09-28 20:07 catalyst
2017-09-21 10:44 catalyst
2017-09-14 10:41 catalyst
2017-09-08 5:27 catalyst
2017-09-01 5:39 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2016-08-18 17:06 catalyst
2016-07-30 13:06 catalyst
2016-07-25 3:10 catalyst
2016-05-30 3:00 catalyst
2016-04-30 13:17 catalyst
2016-01-25 23:07 catalyst
2016-01-18 6:02 catalyst
2016-01-14 19:51 catalyst
2015-12-28 3:00 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=20151228041908.3B3DEE006E@lantean.jmbsvicetto.name \
--to=catalyst@lantean.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