Bug 166420 - portage autoresume point isn't cleared at end of stage run
Bug#: 166420 Product:  Gentoo Hosted Projects Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: catalyst@gentoo.org Reported By: agaffney@gentoo.org
Component: Catalyst
URL: 
Summary: portage autoresume point isn't cleared at end of stage run
Keywords:  InSVN
Status Whiteboard: 
Opened: 2007-02-11 21:31 0000
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.