[gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage3-nomultilib.spec

[catalyst@poseidon.amd64.dev.gentoo.org]

 * just delete the rules file
 * 	rm /etc/udev/rules.d/70-persistent-net.rules
 * and then reboot.
 * 
 * This may however number your devices in a different way than they are now.
 * 
 * If you build an initramfs including udev, then please
 * make sure that the /sbin/udevadm binary gets included,
 * and your scripts changed to use it,as it replaces the
 * old helper apps udevinfo, udevtrigger, ...
 * 
 * mount options for directory /dev are no longer
 * set in /etc/udev/udev.conf, but in /etc/fstab
 * as for other directories.
 * 
 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
 * then please migrate over to using the device names
 * /dev/md*, /dev/loop* and /dev/ram*.
 * The devfs-compat rules have been removed.
 * For reference see Bug #269359.
 * 
 * Rules for /dev/hd* devices have been removed
 * Please migrate to libata.
 * 
 * For more information on udev on Gentoo, writing udev rules, and
 *          fixing known issues visit:
 *          http://www.gentoo.org/doc/en/udev-guide.xml
 * Messages for package dev-vcs/git-1.7.3.4-r1:
 * These additional scripts need some dependencies:
 *   git-quiltimport  : dev-util/quilt
 *   git-instaweb     : || ( www-servers/lighttpd www-servers/apache )
 * Messages for package sys-apps/coreutils-8.14:
 * 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 net-misc/wget-1.12-r3:
 * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc
 * Messages for package sys-fs/e2fsprogs-1.42:
 * No /etc/mtab file, creating one temporarily
 * Messages for package sys-libs/pam-1.1.5:
 * 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-auth/pambase-20101024-r2:
 * Starting from version 20080801, pambase optionally enables
 * SHA512-hashed passwords. For this to work, you need sys-libs/pam-1.0.1
 * built against sys-libs/glibc-2.7 or later.
 * If you don't have support for this, it will automatically fallback
 * to MD5-hashed passwords, just like before.
 * 
 * Please note that the change only affects the newly-changed passwords
 * and that SHA512-hashed passwords will not work on earlier versions
 * of glibc or Linux-PAM.
 * Messages for package sys-apps/openrc-0.9.8.4:
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.
 * 
 * Please read the migration guide available at:
 * http://www.gentoo.org/doc/en/openrc-migration.xml
 * Messages for package sys-apps/busybox-1.19.3-r1:
 * Could not locate user configfile, so we will save a default one
 * Your configuration for sys-apps/busybox-1.19.3-r1 has been saved in 
 * /etc/portage/savedconfig/sys-apps/busybox-1.19.3-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}]
 * This ebuild has support for user defined configs
 * Please read this ebuild for more details and re-emerge as needed
 * if you want to add or remove functionality for busybox
 * Messages for package net-misc/openssh-5.9_p1-r4:
 * Starting with openssh-5.8p1, the server will default to a newer key
 * algorithm (ECDSA).  You are encouraged to manually update your stored
 * keys list as servers update theirs.  See ssh-keyscan(1) for more info.
 * Remember to merge your config files in /etc/ssh/ and then
 * reload sshd: '/etc/init.d/sshd reload'.
 * Please be aware users need a valid shell in /etc/passwd
 * in order to be allowed to login.






































removing /release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120412/tmp/chroot-functions.sh from the chroot
--- Running action sequence: preclean
copying stage3-preclean-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120412/tmp/
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120412/tmp/
Running stage3-preclean-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120412/
>>> Regenerating /etc/ld.so.cache...
emerge  --depclean --with-bdeps=n
!!! CONFIG_PROTECT is empty

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 * 
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.
!!! You have no world file.
!!! Proceeding is likely to break your installation.

Calculating dependencies  \b\b... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   >=sys-libs/ncurses-5.2[unicode] pulled in by:
 *     app-editors/nano-2.2.5
 * 
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 * 
 *   emerge --update --newuse --deep --with-bdeps=y @world
 * 
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 * 
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.

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


!!! catalyst: preclean script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1167, in preclean
    " preclean","preclean script failed.",env=self.env)
  File "/usr/lib64/catalyst/modules/catalyst_support.py", line 542, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Build failed, could not execute preclean

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 1172, in preclean
    raise CatalystError, "Build failed, could not execute preclean"
CatalystError
!!! catalyst: Error encountered during run of target stage3
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120412/.catalyst_lock'



Full build log at /tmp/catalyst-auto.32109/log/hardened_stage3-nomultilib.log