Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71117 - catalyst 1.1.1 croaks in a stage1 build trying to use "--newuse"
Summary: catalyst 1.1.1 croaks in a stage1 build trying to use "--newuse"
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: Catalyst (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: John Davis (zhen) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-13 20:23 UTC by M. Edward Borasky
Modified: 2004-11-22 15:28 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description M. Edward Borasky 2004-11-13 20:23:26 UTC
I just installed catalyst 1.1.1 and am attempting to go through the build process; the eventual goal is a custom LiveCD. I made it through the "snapshot" part, but 

catalyst -f stage1.spec

died with the following message:

 ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the
    tbz2's in the packages directory. Note: This can take a very long time.
!!! Error: --newuse is an invalid option.

!!! catalyst: build script failed

!!! catalyst: Stage build aborting due to error.
!!! catalyst: could not complete build


Here's the spec file:
## generic installation stage specfile
## used to build a stage1, stage2, or stage3 installation tarball

## John Davis <zhen@gentoo.org>

# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer
# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches.
# example:
# subarch: athlon-xp
subarch: i686

# version stamp is an identifier for the build. can be anything you want it to be, but it
# is usually a date.
# example:
# version_stamp: 2004.2
version_stamp: 20041113-znmeb

# target specifies what type of build Catalyst is to do. check the catalyst reference manual
# for supported targets.
# example:
# target: stage2
target: stage1

# rel_type defines what kind of build we are doing. usually, default will suffice.
# example:
# rel_type: default
rel_type: default

# system profile used to build the media
# example:
# profile: default-x86-2004.0
profile: science-i686-2004.2

# which snapshot to use
# example:
# snapshot: 20040614
snapshot: 20041113-znmeb

# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf)
# example:
# default/stage3-x86-2004.1
source_subpath: default/stage3-i686-2004.2
Comment 1 M. Edward Borasky 2004-11-13 20:41:33 UTC
More clues -- it breaks the same way with catalyst 1.1.0. I'm trying it with 1.0.9, and it looks like it has gotten past the breaking point.

Comment 2 John Davis (zhen) (RETIRED) gentoo-dev 2004-11-22 15:28:26 UTC
try using a 2004.3 stage3 or rolling your own stage3 with catalyst. the version of portage in the 2004.2 tarball does not contain an up-to-date version of portage (which honors the --newuse option)