public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@poseidon.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - installcd-stage1.spec
Date: Tue, 24 May 2011 13:27:44 +0000 (UTC)	[thread overview]
Message-ID: <20110524132744.903B4143640@poseidon.amd64.dev.gentoo.org> (raw)




 * Linux kernels >=2.6.9 support memory locking for unprivileged processes.
 * The soft resource limit for memory locking specifies the limit an
 * unprivileged process may lock into memory. You can also use POSIX
 * capabilities to allow pinentry to lock memory. To do so activate the caps
 * USE flag and add the CAP_IPC_LOCK capability to the permitted set of
 * your users.
 * Messages for package app-accessibility/brltty-4.2:
 * 
 * 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-misc/screen-4.0.3-r4:
 * Some dangerous key bindings have been removed or changed to more safe values.
 * We enable some xterm hacks in our default screenrc, which might break some
 * applications. Please check /etc/screenrc for information on these changes.
 * Messages for package net-dialup/rp-pppoe-3.8-r2:
 * Use pppoe-setup to configure your dialup connection.
 * Messages for package net-misc/ntp-4.2.6_p3:
 * You can find an example /etc/ntp.conf in /usr/share/ntp/
 * Review /etc/ntp.conf to setup server info.
 * Review /etc/conf.d/ntpd to setup init.d info.
 * The way ntp sets and maintains your system time has changed.
 * Now you can use /etc/init.d/ntp-client to set your time at
 * boot while you can use /etc/init.d/ntpd to maintain your time
 * while your machine runs
 * Messages for package net-wireless/iwl3945-ucode-15.32.2.9:
 * 
 * Due to ucode API change this version of ucode works only with kernels
 * >=2.6.29-rc1. If you have to use older kernels please install ucode
 * with older API:
 * emerge net-wireless/iwl3945-ucode:0
 * For more information take a look at bugs.gentoo.org/246045
 * 
 * Messages for package net-wireless/iwl4965-ucode-228.61.2.24:
 * Due to ucode API change this version of ucode works only with kernels
 * >=2.6.27. If you need ucode for older versions please install it with
 * emerge net-wireless/iwl4965-ucode:0
 * For more information take a look at bugs.gentoo.org/235007
 * Messages for package sys-fs/mdadm-3.1.4:
 * If using baselayout-2 and not relying on kernel auto-detect
 * of your RAID devices, you need to add 'mdraid' to your 'boot'
 * runlevel. Run the following command:
 * rc-update add mdraid boot
 * Messages for package app-misc/livecd-tools-1.0.42:
 * This package is designed for use on the LiveCD only and will do
 * unspeakably horrible and unexpected things on a normal system.
 * YOU HAVE BEEN WARNED!!!
 * Messages for package sys-fs/lvm2-2.02.73-r1:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Building shared LVM, it will not work inside genkernel!
 * USE flag nocman is deprecated and replaced
 * with the cman USE flag.
 * 
 * USE flags clvm and cman are masked
 * by default and need to be unmasked to use them
 * 
 * If you are using genkernel and root-on-LVM, rebuild the initramfs.
 * lvm volumes are no longer automatically created for
 * baselayout-2 users. If you are using baselayout-2, be sure to
 * run: # rc-update add lvm boot
 * Do NOT add it if you are using baselayout-1 still.
 * Messages for package sys-apps/hwsetup-1.2-r1:
 * This package is designed for use on the LiveCD only and will do 
 * unspeakably horrible and unexpected things on a normal system.
 * YOU HAVE BEEN WARNED!!!
 * This package is intended for usage on the Gentoo release media.  If
 * you are not building a CD, remove this package.  It will not work
 * properly on a running system, as Gentoo does not use any of the
 * Knoppix-style detection except for CD builds.
 * Messages for package app-crypt/gnupg-2.0.17:
 * If you wish to view images emerge:
 * media-gfx/xloadimage, media-gfx/xli or any other viewer
 * Remember to use photo-viewer option in configuration file to activate
 * the right viewer.
 * Please remember to restart gpg-agent if a different version
 * of the agent is currently used. If you are unsure of the gpg
 * agent you are using please run 'killall gpg-agent',
 * and to start a fresh daemon just run 'gpg-agent --daemon'.
 * Messages for package sys-fs/cryptsetup-1.1.3-r3:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * This ebuild introduces a new set of scripts and configuration
 * than the last version. If you are currently using /etc/conf.d/cryptfs
 * then you *MUST* copy your old file to:
 * /etc/conf.d/dmcrypt
 * Or your encrypted partitions will *NOT* work.
 * Please see the example for configuring a LUKS mountpoint
 * in /etc/conf.d/dmcrypt
 * 
 * If you are using baselayout-2 then please do:
 * rc-update add dmcrypt boot
 * This version introduces a command line arguement 'key_timeout'.
 * If you want the search for the removable key device to timeout
 * after 10 seconds add the following to your bootloader config:
 * key_timeout=10
 * A timeout of 0 will mean it will wait indefinitely.
 * 
 * Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use
 * a compatibility mode when using cryptsetup-1.1.x. This can be
 * done by specifying the cipher (-c), key size (-s) and hash (-h).
 * For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup
 * Messages for package sys-fs/dmraid-1.0.0_rc14:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * DMRAID should be safe to use, but no warranties can be given
 * Messages for package app-admin/syslog-ng-3.1.4:
 * It is highly recommended that app-admin/logrotate be emerged to
 * manage the log files.  syslog-ng installs a file in /etc/logrotate.d
 * for logrotate to use.
 * Messages for package sys-fs/evms-2.5.5-r11:
 * ERROR: sys-fs/evms-2.5.5-r11 failed (compile phase):
 *   Failed emake
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 3920:  Called die
 * The specific snippet of code:
 *       emake || die "Failed emake"
 * 
 * If you need support, post the output of 'emerge --info =sys-fs/evms-2.5.5-r11',
 * the complete build log and the output of 'emerge -pqv =sys-fs/evms-2.5.5-r11'.
 * The complete build log is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/environment'.
 * S: '/var/tmp/portage/sys-fs/evms-2.5.5-r11/work/evms-2.5.5'










































 * Regenerating GNU info directory index...
 * Processed 90 info files.

 * IMPORTANT: 3 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


!!! catalyst: Error in attempt to build packages


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

!!! catalyst: livecdbuild aborting due to error.

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



Full build log at /tmp/catalyst-auto.14794/log/installcd-stage1.log



             reply	other threads:[~2011-05-24 13:27 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 13:27 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-13 21:49 [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - installcd-stage1.spec catalyst
2019-05-29  5:13 catalyst
2018-12-08  0:48 catalyst
2018-12-05  4:41 catalyst
2018-07-11  4:38 catalyst
2018-06-14  0:05 catalyst
2018-06-12  0:03 catalyst
2018-06-09  0:27 catalyst
2018-06-07  0:07 catalyst
2018-06-05  0:09 catalyst
2018-06-02  0:04 catalyst
2018-05-31  0:11 catalyst
2018-05-30  4:25 catalyst
2018-05-29  0:07 catalyst
2018-05-26  0:03 catalyst
2018-05-24  0:05 catalyst
2018-05-23  4:24 catalyst
2018-05-17  0:04 catalyst
2018-05-16  4:32 catalyst
2018-05-15  0:22 catalyst
2018-05-12  0:02 catalyst
2018-05-10  0:05 catalyst
2018-05-09  4:24 catalyst
2018-05-08  0:05 catalyst
2018-05-05  0:03 catalyst
2018-05-03  0:03 catalyst
2018-05-02  4:22 catalyst
2018-05-01  0:01 catalyst
2018-04-28  0:05 catalyst
2018-04-26  0:05 catalyst
2018-04-25  4:38 catalyst
2018-04-24  0:56 catalyst
2017-12-06  7:09 catalyst
2017-11-29  7:06 catalyst
2017-11-28  6:03 catalyst
2017-11-22  7:42 catalyst
2017-11-21  6:46 catalyst
2017-11-15  6:55 catalyst
2017-11-14  5:52 catalyst
2017-11-08  6:56 catalyst
2017-11-07  5:53 catalyst
2017-11-01  6:59 catalyst
2017-10-31  5:43 catalyst
2017-10-26  3:25 catalyst
2017-10-24  5:49 catalyst
2017-10-17  5:44 catalyst
2017-10-11  7:10 catalyst
2017-10-10  5:47 catalyst
2017-10-04  7:25 catalyst
2017-10-03  5:44 catalyst
2016-12-20  5:11 catalyst
2016-07-19  5:47 catalyst
2016-07-13  8:19 catalyst
2016-07-12  6:00 catalyst
2016-07-06  6:20 catalyst
2016-07-05  5:55 catalyst
2016-06-29  6:22 catalyst
2016-06-28  5:53 catalyst
2016-06-22  6:11 catalyst
2016-06-15  6:19 catalyst
2016-06-08  6:11 catalyst
2016-01-13  7:29 catalyst
2016-01-12  4:41 catalyst
2015-12-29  6:00 catalyst
2015-07-21  4:56 catalyst
2015-03-11  6:51 catalyst
2015-02-24  4:25 catalyst
2014-09-09  4:44 catalyst
2014-08-27  5:36 catalyst
2014-06-03  5:40 catalyst
2012-09-11 19:11 catalyst
2012-08-21 13:10 catalyst
2012-05-08 13:33 catalyst
2012-05-01 13:28 catalyst
2012-04-24 13:29 catalyst
2012-04-17 13:21 catalyst
2012-04-10 13:22 catalyst
2012-04-03 13:23 catalyst
2012-03-27 13:16 catalyst
2012-03-20 13:07 catalyst
2012-03-13 13:03 catalyst
2011-08-30 12:23 catalyst
2011-05-31 15:38 catalyst
2011-05-03 12:25 catalyst
2011-04-05 11:09 catalyst
2011-01-25 10:49 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=20110524132744.903B4143640@poseidon.amd64.dev.gentoo.org \
    --to=catalyst@poseidon.amd64.dev.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