Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 166426
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Catalyst Developers <catalyst@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Andrew Gaffney <agaffney@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
catalyst_stage1_portage.patch patch to upgrade portage in stage1 target before emerging stuff to ROOT patch Andrew Gaffney 2007-02-11 21:56 0000 398 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 166426 depends on: Show dependency tree
Bug 166426 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-02-11 21:56 0000 
In other stages, we upgrade/re-emerge portage before doing anything else, but
we don't seem to do that in stage1. This is needed to resolve the
coreutils/automake problem we've been encountering lately. I'm attaching a
patch to upgrade portage in the extracted stage3 seed before emerging stuff to
ROOT.

------- Comment #1 From Andrew Gaffney 2007-02-11 21:56:51 0000 ------- 
Created an attachment (id=109901) [details]
patch to upgrade portage in stage1 target before emerging stuff to ROOT

------- Comment #2 From Chris Gianelloni (RETIRED) 2007-02-12 21:54:07 0000 ------- 
Added to SVN for 2.0.3's release...

------- Comment #3 From Chris Gianelloni (RETIRED) 2007-03-20 17:17:24 0000 ------- 
This is fixed in 2.0.3 which should be hitting the tree shortly.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug