public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/admincd-stage1.spec
Date: Mon,  5 Jan 2015 16:15:49 +0000 (UTC)	[thread overview]
Message-ID: <20150105161549.91F90E006A@lantean.jmbsvicetto.name> (raw)




 * Some optional features may require installation of additional
 * packages, like app-portage/gentoolkit-dev for echangelog.
 * 
 * (Note: Above message is only printed the first time package is
 * installed. Please look at /usr/share/doc/ebuild-mode-1.27/README.gentoo*
 * for future reference)

 * Messages for package app-shells/gentoo-bashcomp-20121024:

 * To enable command-line completion for gentoo-bashcomp, run:
 * 
 *   eselect bashcomp enable gentoo
 * 
 * to install locally, or
 * 
 *   eselect bashcomp enable --global gentoo
 * 
 * to install system-wide. (and/or repoman instead of gentoo if you use
 * repoman frequently)

 * Messages for package sys-apps/openrc-0.12.4:

 * In this version of OpenRC, the loopback interface no longer
 * satisfies the net virtual.
 * If you have services now which do not start because of this,
 * They can be fixed by adding rc_need="!net"
 * to the /etc/conf.d/<servicename> file.
 * You should also file a bug against the service asking that
 * need net be dropped from the dependencies.
 * The bug you file should block the following tracker:
 * https://bugs.gentoo.org/show_bug.cgi?id=439092
 * This version of OpenRC doesn't enable nfs mounts automatically any
 * longer. In order to mount nfs file systems, you must use the
 * nfsmount service from the nfs-utils package.
 * See bug https://bugs.gentoo.org/show_bug.cgi?id=427996 for
 * more information on this.
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.

 * Messages for package sys-fs/fuse-2.9.3:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version

 * Messages for package dev-python/pypam-0.5.0-r2:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/pyopenssl-0.13.1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/m2crypto-0.21.1-r2:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/ndg-httpsclient-0.3.2:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/pyasn1-0.1.7:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/chardet-2.2.1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/requests-2.3.0:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/ssl-fetch-0.2:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/markdown-2.5.1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/lockfile-0.9.1-r1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/pycrypto-2.6.1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/ecdsa-0.11-r1:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-python/paramiko-1.13.0:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package dev-lang/python-3.4.1:

 * You have just upgraded from an older version of Python.
 * 
 * Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules.

 * Messages for package app-accessibility/brltty-5.0-r3:

 * 
 * please be sure /etc/brltty.conf is correct for your system.
 * 
 * To make brltty start on boot, type this command as root:
 * 
 * rc-update add brltty boot

 * Messages for package app-admin/hddtemp-0.3_beta15-r7:

 * In order to update your hddtemp database, run:
 * emerge --config =app-admin/hddtemp-0.3_beta15-r7
 * 
 * If your hard drive is not recognized by hddtemp, please consider
 * submitting your HDD info for inclusion into the Gentoo hddtemp
 * database by filing a bug at https://bugs.gentoo.org/
 * 
 * If hddtemp complains but finds your HDD temperature sensor, use the
 * --quiet option to suppress the warning.
 * 
 * (Note: Above message is only printed the first time package is
 * installed. Please look at /usr/share/doc/hddtemp-0.3_beta15-r7/README.gentoo*
 * for future reference)

 * Messages for package app-editors/hexcurse-1.55:

 * ERROR: app-editors/hexcurse-1.55::gentoo failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *            ebuild.sh, line   93:  Called src_configure
 *          environment, line 2644:  Called default
 *   phase-functions.sh, line  770:  Called default_src_configure
 *   phase-functions.sh, line  805:  Called __eapi2_src_configure
 *     phase-helpers.sh, line  691:  Called econf
 *     phase-helpers.sh, line  584:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 * 
 * If you need support, post the output of `emerge --info '=app-editors/hexcurse-1.55::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-editors/hexcurse-1.55::gentoo'`.
 * The complete build log is located at '/var/log/portage/app-editors:hexcurse-1.55:20150105-161542.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-editors/hexcurse-1.55/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-editors/hexcurse-1.55/temp/environment'.
 * Working directory: '/var/tmp/portage/app-editors/hexcurse-1.55/work/hexcurse-1.55'
 * S: '/var/tmp/portage/app-editors/hexcurse-1.55/work/hexcurse-1.55'

!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1403, in build_packages
    "Error in attempt to build packages",env=self.env)
  File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: livecdbuild aborting due to error.

Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1408, in build_packages
    "build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage1
Catalyst aborting....
lockfile does not exist '/home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage1-amd64-20150105/.catalyst_lock'



Full build log at /home/release/tmp/run/catalyst-auto.11FAEg/log/hardened_admincd-stage1.log


             reply	other threads:[~2015-01-05 16:15 UTC|newest]

Thread overview: 198+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 16:15 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-03  2:30 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/admincd-stage1.spec catalyst
2023-06-06  3:47 catalyst
2023-03-20  0:27 catalyst
2023-02-13  1:54 catalyst
2023-01-16  5:04 catalyst
2022-03-06 20:50 catalyst
2022-02-06 19:00 catalyst
2020-04-23 15:59 catalyst
2020-04-16 15:59 catalyst
2020-01-13 14:31 catalyst
2019-10-21 12:27 catalyst
2019-10-14 13:06 catalyst
2019-10-07 12:36 catalyst
2019-09-30 12:57 catalyst
2019-09-23 12:06 catalyst
2019-09-16 12:52 catalyst
2019-09-09 12:19 catalyst
2019-09-02 12:32 catalyst
2019-08-26 12:07 catalyst
2019-08-19 14:04 catalyst
2019-08-12 12:28 catalyst
2019-08-05 12:26 catalyst
2019-07-29 12:19 catalyst
2019-07-23 10:18 catalyst
2019-05-30 11:33 catalyst
2019-05-29 17:52 catalyst
2019-05-27 11:51 catalyst
2019-05-23 12:32 catalyst
2019-04-15 14:21 catalyst
2019-04-15 13:30 catalyst
2018-12-07  9:54 catalyst
2018-11-26 11:32 catalyst
2018-08-27  9:14 catalyst
2018-06-13  6:01 catalyst
2018-06-11  6:05 catalyst
2018-06-08  6:06 catalyst
2018-06-06  6:05 catalyst
2018-06-04  9:28 catalyst
2018-06-01  6:33 catalyst
2018-05-30  6:36 catalyst
2018-05-28 10:03 catalyst
2018-05-28  6:21 catalyst
2018-05-25  6:27 catalyst
2018-05-23  9:02 catalyst
2018-05-21  8:36 catalyst
2018-05-18  6:34 catalyst
2018-05-16  7:13 catalyst
2018-05-14  9:03 catalyst
2018-05-14  6:30 catalyst
2018-05-11  6:20 catalyst
2018-05-09  6:37 catalyst
2018-05-07  8:30 catalyst
2018-05-07  6:22 catalyst
2018-05-04  6:22 catalyst
2018-05-02  6:21 catalyst
2018-04-30 10:08 catalyst
2018-04-30  6:27 catalyst
2018-04-27  6:24 catalyst
2018-04-25  4:10 catalyst
2018-04-23  9:23 catalyst
2018-01-05  9:17 catalyst
2018-01-04  5:40 catalyst
2018-01-01 11:17 catalyst
2017-12-31 22:57 catalyst
2017-12-19  2:59 catalyst
2017-12-16 14:48 catalyst
2017-12-15  0:15 catalyst
2017-12-15  0:14 catalyst
2017-12-14  7:07 catalyst
2017-12-08  4:55 catalyst
2017-12-06  1:16 catalyst
2017-12-01  0:30 catalyst
2017-11-24  3:46 catalyst
2017-11-16 23:58 catalyst
2017-11-09 23:13 catalyst
2017-11-06 20:19 catalyst
2017-11-02 23:40 catalyst
2017-10-26 22:57 catalyst
2017-10-26  3:25 catalyst
2017-10-26  3:25 catalyst
2017-10-26  3:22 catalyst
2017-10-19 22:52 catalyst
2017-10-16 22:04 catalyst
2017-10-12 22:40 catalyst
2017-10-05 23:17 catalyst
2017-09-08  4:51 catalyst
2017-09-01  5:02 catalyst
2017-08-25  4:12 catalyst
2017-08-18  4:13 catalyst
2017-08-11  4:26 catalyst
2017-08-04  4:21 catalyst
2017-07-28  4:14 catalyst
2017-07-21  4:14 catalyst
2017-07-14  4:17 catalyst
2017-07-07  4:22 catalyst
2017-06-30  4:24 catalyst
2017-06-23  5:37 catalyst
2017-06-16  4:49 catalyst
2017-05-26  4:17 catalyst
2017-05-05  4:35 catalyst
2017-04-28  4:24 catalyst
2017-04-21  7:18 catalyst
2017-04-14  0:21 catalyst
2017-04-07  0:40 catalyst
2017-03-23 23:50 catalyst
2017-03-20 19:35 catalyst
2017-03-17  0:39 catalyst
2017-03-10  0:05 catalyst
2017-03-05  9:23 catalyst
2017-03-03  0:11 catalyst
2017-03-02 17:45 catalyst
2017-03-02  3:39 catalyst
2017-02-17  0:10 catalyst
2016-12-23  0:34 catalyst
2016-12-15 22:03 catalyst
2016-12-01 23:52 catalyst
2016-11-24 23:56 catalyst
2016-11-17 23:22 catalyst
2016-11-03 23:18 catalyst
2016-10-27 23:27 catalyst
2016-08-29 19:38 catalyst
2016-08-25 23:01 catalyst
2016-08-22 19:18 catalyst
2016-07-11 18:28 catalyst
2016-07-04 18:39 catalyst
2016-06-27 18:25 catalyst
2016-06-23 23:36 catalyst
2016-06-20 18:12 catalyst
2016-06-13 18:30 catalyst
2016-06-06 17:55 catalyst
2016-05-23 15:43 catalyst
2016-05-22 15:43 catalyst
2016-05-21 15:45 catalyst
2016-05-20 15:52 catalyst
2016-05-18 15:51 catalyst
2016-05-16 15:53 catalyst
2016-05-15 15:53 catalyst
2016-05-14 15:37 catalyst
2016-05-13 15:42 catalyst
2016-05-11 17:52 catalyst
2016-05-09 15:45 catalyst
2016-05-08 15:47 catalyst
2016-05-06 15:47 catalyst
2016-05-04 15:41 catalyst
2016-05-02 15:43 catalyst
2016-05-01 15:42 catalyst
2016-04-30 13:17 catalyst
2016-04-29 15:45 catalyst
2016-04-21 20:48 catalyst
2016-04-07 20:42 catalyst
2016-03-31 18:22 catalyst
2016-01-25 22:42 catalyst
2016-01-11 20:16 catalyst
2016-01-07 14:36 catalyst
2015-12-10 14:58 catalyst
2015-10-31 19:43 catalyst
2015-07-23 13:09 catalyst
2015-07-16 12:19 catalyst
2015-05-21 13:19 catalyst
2015-03-30 21:00 catalyst
2014-12-01 20:24 catalyst
2014-10-13 11:32 catalyst
2014-09-29 10:52 catalyst
2014-09-22 10:44 catalyst
2014-09-18 10:25 catalyst
2014-09-15  9:20 catalyst
2014-09-04 13:56 catalyst
2014-08-28 13:26 catalyst
2014-08-25 11:06 catalyst
2014-08-21 13:32 catalyst
2014-08-14 15:15 catalyst
2014-08-14 13:17 catalyst
2014-08-11 11:11 catalyst
2014-08-07 13:35 catalyst
2014-08-07 12:12 catalyst
2014-08-04 12:58 catalyst
2014-07-31 16:31 catalyst
2014-07-31 15:34 catalyst
2014-07-24 14:58 catalyst
2014-07-24 13:58 catalyst
2014-07-20  0:41 catalyst
2014-07-17 14:42 catalyst
2014-07-10 10:27 catalyst
2014-07-07 17:34 catalyst
2014-07-03 14:52 catalyst
2014-06-26 15:19 catalyst
2014-06-19 15:07 catalyst
2014-05-29 15:18 catalyst
2014-05-22 15:55 catalyst
2014-05-15 14:41 catalyst
2014-05-08 14:47 catalyst
2014-05-01 14:03 catalyst
2014-04-28 17:05 catalyst
2014-04-14 17:55 catalyst
2014-04-10 14:55 catalyst
2014-04-03 20:42 catalyst
2014-04-03 12:31 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=20150105161549.91F90E006A@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