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 - hardened/stage4-nomultilib-cloud.spec
Date: Fri, 24 Nov 2017 10:07:32 +0000 (UTC)	[thread overview]
Message-ID: <20171124100732.D635934FBD@nightheron.gentoo.org> (raw)




Catalyst, version 2.0.19
Copyright 2003-2008 Gentoo Foundation
Copyright 2008-2012 various authors
Distributed under the GNU General Public License version 2.1

Using command line specified Catalyst configuration file, /etc/catalyst/release/amd64-auto.conf
Setting sharedir to config file value "/usr/lib64/catalyst/"
Setting snapshot_cache to config file value "/release/tmp/snapshots"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/release/buildroot/amd64-dev"
Setting portdir to config file value "/release/trees/portage-auto"
Setting distdir to config file value "/release/tmp/distfiles/"
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Preserving libs during unmerge.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.

Traceback (most recent call last):
  File "/usr/lib64/catalyst/modules/catalyst/config.py", line 27, in parse_file
    myf = open(filename, "r")
IOError: [Errno 2] No such file or directory: 'hardened/stage4-nomultilib-cloud.spec'
None

!!! catalyst: Could not open file hardened/stage4-nomultilib-cloud.spec

Traceback (most recent call last):
  File "/usr/lib64/catalyst/catalyst", line 374, in <module>
    spec = modules.catalyst.config.SpecParser(myspecfile)
  File "/usr/lib64/catalyst/modules/catalyst/config.py", line 112, in __init__
    self.parse_file(filename)
  File "/usr/lib64/catalyst/modules/catalyst/config.py", line 29, in parse_file
    raise CatalystError, "Could not open file " + filename
modules.catalyst_support.CatalystError
Command exited with non-zero status 1
0.05user 0.01system 0:00.07elapsed 98%CPU (0avgtext+0avgdata 60592maxresident)k
0inputs+8outputs (0major+3110minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20171123.muQaFS/log/hardened_stage4-nomultilib-cloud.log


             reply	other threads:[~2017-11-24 10:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 10:07 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-nomultilib-cloud.spec catalyst
2017-12-03 20:48 catalyst
2017-12-03 20:41 catalyst
2017-12-01  6:18 catalyst
2017-11-17  5:08 catalyst
2017-11-10  4:15 catalyst
2017-11-03  4:44 catalyst
2017-10-27  4:00 catalyst
2017-10-20  3:55 catalyst
2017-10-13  3:37 catalyst
2017-10-06  4:26 catalyst
2017-09-28 23:16 catalyst
2017-09-21 11:41 catalyst
2017-09-14 11:37 catalyst
2017-09-08 11:08 catalyst
2017-09-01  8:06 catalyst
2017-03-31  8:21 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2016-08-18 17:07 catalyst
2016-07-30 13:09 catalyst
2016-07-25  3:14 catalyst
2016-07-11 20:17 catalyst
2016-05-30  3:00 catalyst
2016-04-30 13:17 catalyst
2016-01-26  3:16 catalyst
2016-01-18  6:57 catalyst
2016-01-15  0:19 catalyst
2015-12-28  4:19 catalyst
2015-12-28  3:00 catalyst
2015-12-26 12:44 catalyst
2015-12-25  8:33 catalyst
2015-12-25  8:28 catalyst
2015-12-24 18:16 catalyst
2015-12-18  3:08 catalyst
2015-12-18  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=20171124100732.D635934FBD@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