Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 123584 - catalyst 2.0_rc39 fails to build stage (1) when using portage 2.1_pre
Summary: catalyst 2.0_rc39 fails to build stage (1) when using portage 2.1_pre
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: Catalyst (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Catalyst Developers
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2006-02-21 00:48 UTC by Rafael
Modified: 2006-04-18 17:16 UTC (History)
0 users

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


Attachments
catalyst-2.0_rc39 fix for build.py with portage-2.1_pre* (catalyst-2.0_rc39-build_py-portage21.patch,1.25 KB, patch)
2006-02-21 00:50 UTC, Rafael
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael 2006-02-21 00:48:12 UTC
When building a stage (stage1 in this case caused it)
catalyst (2.0_rc39) bails out with following:

==========================================================
Traceback (most recent call last):
  File "/tmp/build.py", line 18, in ?
    pkgs = scan_profile("packages")
  File "/tmp/build.py", line 15, in scan_profile
    return portage.stack_lists( portage.grab_multiple(file, portage.settings.profiles, portage.grabfile), incremental=1);
AttributeError: 'module' object has no attribute 'grab_multiple'
Your profile seems to be broken.
Could not build a list of build packages.
Double check your /etc/make.profile link and the 'packages' files.

!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1036, in run_local
    cmd("/bin/bash "+self.settings["controller_file"]+" run","run script failed.",env=self.env)
  File "/usr/lib/catalyst2/modules/catalyst_support.py", line 485, in cmd
    raise CatalystError,myexc
CatalystError: <unprintable instance object>
None

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


This happens using portage-2.1_pre4-r1, buildsystem as well as seed stage.

I investigated and found a fix letting me proceed with the build without
errors. Patch follows in attachment.
It adds another "if else" to not break compatibility with previous
portage versions. This fix must not necessarily be correct, but WORKSFORME ;)

Apply to the "build.py" file (for stage1 in /usr/lib/catalyst2/targets/stage1, other targets _probably_ also need it in /usr/lib/catalyst2/modules)

cheers,

Rafael
Comment 1 Rafael 2006-02-21 00:50:48 UTC
Created attachment 80353 [details, diff]
catalyst-2.0_rc39 fix for build.py  with portage-2.1_pre*

Proposed patch.
Comment 2 Rafael 2006-02-21 01:02:19 UTC
(In reply to comment #0)
> other targets _probably_ also need it in /usr/lib/catalyst2/modules)
> 
Err, probably there is no build.py in there, my bad, i saw builder.py :S
Comment 3 Rafael 2006-03-14 00:36:09 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > other targets _probably_ also need it in /usr/lib/catalyst2/modules)
> > 
> Err, probably there is no build.py in there, my bad, i saw builder.py :S
> 
Sorry for this comment, i just read it and doesn't make much sense i think. What was meant is that this is only a problem with /usr/lib/catalyst2/targets/stage1/build.py, the patch still applies.


Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2006-04-17 14:41:18 UTC
Patch has been added... thanks for the bug report!
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2006-04-18 17:16:39 UTC
Fixed in 2.0_rc42