First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 166420
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_portage_autoresume.patch patch to clear portage autoresume point patch Andrew Gaffney 2007-02-11 21:32 0000 536 bytes Details | Diff
catalyst_remove_portage_autoresume_check.patch patch to remove check for autoresume point in setup_portage() patch Andrew Gaffney 2007-02-11 22:03 0000 834 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 166420 depends on: Show dependency tree
Bug 166420 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:31 0000 
Since the portage autoresume point is put at /tmp/.clst_portage inside the
chroot, it isn't removed as part of the normal autoresume cleanup code. I'm
attaching a small patch that should take care of this special case.

------- Comment #1 From Andrew Gaffney 2007-02-11 21:32:21 0000 ------- 
Created an attachment (id=109898) [details]
patch to clear portage autoresume point

------- Comment #2 From Andrew Gaffney 2007-02-11 21:59:55 0000 ------- 
Alternatively, we can just kill the autoresume check for portage like you've
done for ccache and distcc, since it takes very little time to emerge portage.
That's probably the better solution. That will allow the patch in bug 166426 to
be used with pre-existing stage3 seeds.

------- Comment #3 From Andrew Gaffney 2007-02-11 22:03:15 0000 ------- 
Created an attachment (id=109903) [details]
patch to remove check for autoresume point in setup_portage()

------- Comment #4 From Chris Gianelloni (RETIRED) 2007-02-12 22:08:14 0000 ------- 
I've gone w/ approach #2

------- Comment #5 From Chris Gianelloni (RETIRED) 2007-03-20 17:17:23 0000 ------- 
This is fixed in 2.0.3 which should be hitting the tree shortly.
First Last Prev Next    No search results available      Search page      Enter new bug