[gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - installcd-stage1.spec

* http://www.gentoo.org/doc/en/power-management-guide.xml
 * 

 * Messages for package net-wireless/wpa_supplicant-2.4-r3:

 * If this is a clean installation of wpa_supplicant, you
 * have to create a configuration file named
 * /etc/wpa_supplicant/wpa_supplicant.conf
 * 
 * An example configuration file is available for reference in
 * /usr/share/doc/wpa_supplicant-2.4-r3/

 * Messages for package net-misc/dhcpcd-6.9.0:

 * 
 * dhcpcd has zeroconf support active by default.
 * This means it will always obtain an IP address even if no
 * DHCP server can be contacted, which will break any existing
 * failover support you may have configured in your net configuration.
 * This behaviour can be controlled with the noipv4ll configuration
 * file option or the -L command line switch.
 * See the dhcpcd and dhcpcd.conf man pages for more details.
 * 
 * Dhcpcd has duid enabled by default, and this may cause issues
 * with some dhcp servers. For more information, see
 * https://bugs.gentoo.org/show_bug.cgi?id=477356
 * 
 * If you activate the lookup-hostname hook to look up your hostname
 * using the dns, you need to install net-dns/bind-tools.

 * Messages for package app-accessibility/brltty-5.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-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-misc/screen-4.0.3-r6:

 * 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-fs/cifs-utils-6.1-r1:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * You must enable CIFS support in your kernel config, 
 * to be able to mount samba shares. You can find it at
 * 
 *   File systems
 * 	Network File Systems
 * 			CIFS support
 * 
 * and recompile your kernel ...
 * setuid use flag was dropped due to multiple security implications
 * such as CVE-2009-2948, CVE-2011-3585 and CVE-2012-1586
 * You are free to set setuid flags by yourself

 * Messages for package app-text/asciidoc-8.6.9-r1:

 * prepcompress: ignoring nonexistent path '/usr/share/doc/asciidoc-8.6.9-r1/examples'

 * Messages for package sys-apps/util-linux-2.25.2-r2:

 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.

 * Messages for package sys-fs/mdadm-3.3.1-r2:

 * If you're not relying on kernel auto-detect of your RAID
 * devices, you need to add 'mdraid' to your 'boot' runlevel:
 * 	rc-update add mdraid boot

 * Messages for package sys-apps/coreutils-8.23:

 * Make sure you run 'hash -r' in your active shells.
 * You should also re-source your shell settings for LS_COLORS
 *   changes, such as: source /etc/profile

 * Messages for package sys-libs/pam-1.2.1:

 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | egrep -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.

 * Messages for package sys-apps/busybox-1.23.1-r1:

 * Could not locate user configfile, so we will save a default one
 * You cannot have USE='static pam'.  Assuming static is more important.
 * Your configuration for sys-apps/busybox-1.23.1-r1 has been saved in 
 * /etc/portage/savedconfig/sys-apps/busybox-1.23.1-r1 for your editing pleasure.
 * You can edit these files by hand and remerge this package with
 * USE=savedconfig to customise the configuration.
 * You can rename this file/directory to one of the following for
 * its configuration to apply to multiple versions:
 * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
 * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]

 * Messages for package sys-libs/libkudzu-1.2.57.1:

 * 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 sys-apps/hwsetup-1.2-r3:

 * 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 use 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 sys-fs/udev-216:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * 
 * Starting from version >= 197 the new predictable network interface names are
 * used by default, see:
 * http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
 * http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c
 * 
 * Example command to get the information for the new interface name before booting
 * (replace <ifname> with, for example, eth0):
 * # udevadm test-builtin net_id /sys/class/net/<ifname> 2> /dev/null
 * 
 * You can use either kernel parameter "net.ifnames=0", create empty
 * file /etc/systemd/network/99-default.link, or symlink it to /dev/null
 * to disable the feature.
 * 
 * You need to restart udev as soon as possible to make the upgrade go
 * into effect.
 * The method you use to do this depends on your init system.
 * For sys-apps/openrc users it is:
 * # /etc/init.d/udev --nodeps restart
 * 
 * For more information on udev on Gentoo, upgrading, writing udev rules, and
 * fixing known issues visit:
 * http://wiki.gentoo.org/wiki/Udev
 * http://wiki.gentoo.org/wiki/Udev/upgrade

 * Messages for package sys-fs/xfsprogs-3.2.4:

 * Fetch failed for 'sys-fs/xfsprogs-3.2.4', Log file:
 *  '/var/log/portage/sys-fs:xfsprogs-3.2.4:20150803-072603.log'

!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1432, 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 1333, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1437, 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/default/livecd-stage1-amd64-20150803/.catalyst_lock'



Full build log at /home/release/tmp/run/catalyst-auto.JsEaEy/log/installcd-stage1.log