Bug 97867 – error in stage1 building with broken profile is confusing

• Status: RESOLVED FIXED
• Product: Gentoo Hosted Projects

[Description SpanKY 2005-07-03 22:42:27 UTC]

if you try to build a stage1 and the profile is screwed up/broken/whatever, the error can be confusing:

emerge: please tell me what to do.
 
 
Usage:
   emerge [ options ] [ action ] [ ebuildfile | tbz2file | dependency ] [ ... ]
   emerge [ options ] [ action ] < system | world >
   emerge < --sync | --metadata | --info >
   emerge --resume [ --pretend | --ask | --skipfirst ]
   emerge --help [ system | config | sync ]
Options: -[abcCdDefhikKlnoOpPsSuUvV] [--oneshot] [--newuse] [--noconfmem]
                                    [--columns] [--nospinner]
Actions: [ --clean | --depclean | --inject | --prune | --regen | --search | --unmerge ]
 
 
   For more help try 'emerge --help' or consult the man page.
 
 
None
None
 
!!! catalyst: build script failed

[Comment 1 SpanKY 2005-07-03 22:43:02 UTC]

Created attachment 62575 [details, diff]
sanity-check-stage1.patch

the fix is to make sure that the build.py script actually gave back a list of
packages for us to emerge and if it doesnt, dump a helpful error message and
abort

[Comment 2 Chris Gianelloni (RETIRED) 2005-07-05 08:53:37 UTC]

This patch is against catalyst 2 in CVS and not the catalyst 1.x branch, correct?

[Comment 3 Chris Gianelloni (RETIRED) 2005-07-05 09:10:52 UTC]

nevermind... :P

[Comment 4 Chris Gianelloni (RETIRED) 2005-07-05 10:57:41 UTC]

Fixed... by the way, we don't use eerror... since we don't pull in all the
portage functions