public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@rooster.ppc64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ppc-auto] Catalyst fatal build error - stage3.spec
Date: Sun, 15 May 2011 08:13:49 -0700	[thread overview]
Message-ID: <20110515151508.352171C035@pigeon.gentoo.org> (raw)




>>> Emerging (115 of 137) sys-apps/groff-1.21
>>> Installing (115 of 137) sys-apps/groff-1.21
>>> Emerging (116 of 137) sys-fs/hfsplusutils-1.0.4-r1
>>> Installing (116 of 137) sys-fs/hfsplusutils-1.0.4-r1
>>> Emerging (117 of 137) sys-apps/man-1.6f-r4
>>> Failed to emerge sys-apps/man-1.6f-r4, Log file:
>>>  '/var/tmp/portage/sys-apps/man-1.6f-r4/temp/build.log'
 * Package:    sys-apps/man-1.6f-r4
 * Repository: gentoo
 * Maintainer: base-system@gentoo.org
 * USE:        elibc_glibc kernel_linux nls ppc userland_GNU
 * FEATURES:   sandbox
 * Adding group 'man' to your system ...
 *  - Groupid: 15
/usr/portage/eclass/eutils.eclass: line 860: groupadd: command not found
 * ERROR: sys-apps/man-1.6f-r4 failed (setup phase):
 *   enewgroup failed
 * 
 * Call stack:
 *            ebuild.sh, line  56:  Called pkg_setup
 *   man-1.6f-r4.ebuild, line  24:  Called enewgroup 'man' '15'
 *        eutils.eclass, line 860:  Called die
 * The specific snippet of code:
 *   		groupadd -r ${opts} ${egroup} || die "enewgroup failed"
 * 
 * If you need support, post the output of 'emerge --info =sys-apps/man-1.6f-r4',
 * the complete build log and the output of 'emerge -pqv =sys-apps/man-1.6f-r4'.
 * The complete build log is located at '/var/tmp/portage/sys-apps/man-1.6f-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/man-1.6f-r4/temp/die.env'.
 * S: '/var/tmp/portage/sys-apps/man-1.6f-r4/work/man-1.6f'

 * Messages for package sys-libs/timezone-data-2011e:

 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.

 * Messages for package app-portage/portage-utils-0.3.1:

 * /etc/portage/postsync.d/q-reinitialize has been installed for convenience
 * If you wish for it to be automatically run at the end of every --sync:
 *    # chmod +x /etc/portage/postsync.d/q-reinitialize
 * Normally this should only take a few seconds to run but file systems
 * such as ext3 can take a lot longer.  To disable, simply do:
 *    # chmod -x /etc/portage/postsync.d/q-reinitialize

 * Messages for package sys-libs/glibc-2.11.3:
 * Generating all locales; edit /etc/locale.gen to save time/space


 * Messages for package sys-libs/gdbm-1.8.3-r4:
 * 32bit systems might have to rebuild all gdbm databases due to
 * LFS changes in the gdbm format.  You can either delete the db
 * and regenerate it from scratch, or use the converter:
 * http://bugs.gentoo.org/attachment.cgi?id=215326
 * 
 * See this comment for information on how to use it:
 * http://bugs.gentoo.org/299390#c15
 * 
 * You should be able to locate most gdbm db's on your system with:
 * find /etc /var -type f -exec file {} + | grep 'GNU dbm 1.x or ndbm database'
 * 
 * You could also try using this helper script:
 * http://bugs.gentoo.org/attachment.cgi?id=222581


 * Messages for package sys-fs/udev-151-r4:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 *   CONFIG_IDE:	 should not be set. But it is.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * 
 * udev-151 does not support Linux kernel before version 2.6.25!
 * For a reliable udev, use at least kernel 2.6.27
 * 
 * You need to add the udev init script to the runlevel sysinit,
 * else your system will not be able to boot
 * after updating to >=openrc-0.4.0
 * Run this to enable udev for >=openrc-0.4.0:
 * 	rc-update add udev sysinit
 * 

 * Auto-adding 'udev-postmount' service to your default runlevel
 * 
 * If after the udev update removable devices or CD/DVD drives
 * stop working, try re-emerging HAL before filling a bug report
 * 
 * persistent-net does assigning fixed names to network devices.
 * If you have problems with the persistent-net rules,
 * 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.
 * 
 * This version of udev no longer has devfs-compat enabled
 * 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 will be removed on the next udev update.
 * For reference see Bug #269359.
 * 
 * This version of udev no longer has use flag old-hd-rules enabled
 * So all special rules for /dev/hd* devices are missing
 * Please migrate to the new libata if you need these rules.
 * They will be completely removed on the next udev update.
 * 
 * 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 sys-apps/portage-2.1.9.42:
 * If you are an ebuild developer and you plan to commit ebuilds
 * with this system then please install dev-python/pycrypto or
 * enable the ssl USE flag for >=dev-lang/python-2.6 in order
 * to enable RMD160 hash support.
 * See bug #198398 for more information.


 * Messages for package app-misc/ca-certificates-20090709:
 * You should run update-ca-certificates manually after etc-update


 * 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.7:
 * 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.41.12:
 * No /etc/mtab file, creating one temporarily


 * Messages for package sys-apps/man-1.6f-r4:
 * ERROR: sys-apps/man-1.6f-r4 failed (setup phase):
 *   enewgroup failed
 * 
 * Call stack:
 *            ebuild.sh, line  56:  Called pkg_setup
 *   man-1.6f-r4.ebuild, line  24:  Called enewgroup 'man' '15'
 *        eutils.eclass, line 860:  Called die
 * The specific snippet of code:
 *   		groupadd -r ${opts} ${egroup} || die "enewgroup failed"
 * 
 * If you need support, post the output of 'emerge --info =sys-apps/man-1.6f-r4',
 * the complete build log and the output of 'emerge -pqv =sys-apps/man-1.6f-r4'.
 * The complete build log is located at '/var/tmp/portage/sys-apps/man-1.6f-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/man-1.6f-r4/temp/die.env'.
 * S: '/var/tmp/portage/sys-apps/man-1.6f-r4/work/man-1.6f'

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

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


!!! catalyst: run script failed.


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

!!! catalyst: Stage build aborting due to error.

Traceback (most recent call last):
File "/usr/lib/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 1212, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage3
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage3-ppc-20110515/.catalyst_lock'



Full build log at /tmp/catalyst-auto.4487/log/stage3.log



             reply	other threads:[~2011-05-15 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 15:13 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-15 13:48 [gentoo-releng-autobuilds] [ppc-auto] Catalyst fatal build error - stage3.spec catalyst
2015-05-17 14:36 catalyst
2014-01-19 14:31 catalyst
2014-01-12 14:30 catalyst
2014-01-05 14:29 catalyst
2011-07-17 13:58 catalyst
2011-04-10 13:39 catalyst
2011-03-13 16:14 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=20110515151508.352171C035@pigeon.gentoo.org \
    --to=catalyst@rooster.ppc64.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