From: "Ian P. Christian" <pookey@pookey.co.uk>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] bug when building netboot
Date: Mon, 10 Jul 2006 14:06:23 +0100 [thread overview]
Message-ID: <200607101406.23638.pookey@pookey.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 3049 bytes --]
It's quite probable my spec file is nonsence, but even in these cases I would
expect an error message rather then a backtrace.
spec file: http://pookey.co.uk/temp/test.spec
# catalyst2 -f ./test.spec
Gentoo Catalyst, version 2.0_rc49
Copyright 2003-2005 The Gentoo Foundation
Distributed under the GNU General Public License version 2
Using default Catalyst configuration file, /etc/catalyst2/catalyst2.conf
Setting sharedir to config file value "/usr/lib/catalyst2"
Setting snapshot_cache to default value "/var/tmp/catalyst2/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/catalyst2"
Setting portdir to default value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume ccache kerncache pkgcache
seedcache snapcache"
Compiler cache support enabled.
Package cache support enabled.
Snapshot cache support enabled.
Seed cache support enabled.
Kernel cache support enabled.
Autoresuming support enabled.
WARNING: No value set for key netboot/base_tarball...deleting
WARNING: No value set for key
netboot/packages/reiserfsprogs/files...deleting
WARNING: No value set for key pkgcache_path...deleting
WARNING: No value set for key kerncache_path...deleting
WARNING: No value set for key
netboot/packages/e2fsprogs/files...deleting
WARNING: No value set for key portage_confdir...deleting
WARNING: No value set for key
netboot/packages/xfsprogs/files...deleting
WARNING: No value set for key netboot/use...deleting
WARNING: No value set for key netboot/kernel/use...deleting
WARNING: No value set for key netboot/extra_files...deleting
WARNING: No value set for key
netboot/packages/raidtools/files...deleting
WARNING: No value set for key portage_overlay...deleting
WARNING: No value set for key netboot/busybox_config...deleting
Using target: netboot
Building natively for x86
netboot root path is /tmp/image
Source path set to /var/tmp/catalyst2/builds/stage3-i686-2006.0.tar.bz2
Caching snapshot to /var/tmp/catalyst2/snapshot_cache/20060710/
The autoresume path
is /var/tmp/catalyst2/tmp/default/.autoresume-netboot-i686-20060710/
Location of the package cache
is /var/tmp/catalyst2/packages/default/netboot-i686-20060710/
Location of the kerncache
is /var/tmp/catalyst2/kerncache/default/netboot-i686-20060710/
Catalyst aborting....
Traceback (most recent call last):
File "/usr/bin/catalyst2", line 380, in ?
build_target(addlargs, targetmap)
File "/usr/bin/catalyst2", line 196, in build_target
mytarget=targetmap[addlargs["target"]](conf_values, addlargs)
File "/usr/lib/catalyst2/modules/netboot_target.py", line 43, in __init__
self.set_build_kernel_vars(addlargs)
TypeError: set_build_kernel_vars() takes exactly 1 argument (2 given)
--
Ian P. Christian
http://pookey.co.uk
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-07-10 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 13:06 Ian P. Christian [this message]
2006-07-10 13:39 ` [gentoo-catalyst] bug when building netboot Andrew Gaffney
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=200607101406.23638.pookey@pookey.co.uk \
--to=pookey@pookey.co.uk \
--cc=gentoo-catalyst@lists.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