Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(256)

Issue 4070002: Import portage when it's used to fix broken tree. (Closed)

Created:
10 years, 2 months ago by David James
Modified:
9 years, 7 months ago
Reviewers:
anush, sosa
CC:
chromium-os-reviews_chromium.org, Mandeep Singh Baines, anush, sosa
Visibility:
Public.

Description

Import portage when it's used to fix broken tree. This is just a temporary workaround until buildbots have portage installed outside the chroot. We should roll this back when that's fixed. TBR=sosa@chromium.org BUG=b0rked tree TEST=ran unit tests Change-Id: I004c1476e929212774218d50d10f371806cf6c7f Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=676dff5

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -1 line) Patch
M cros_mark_as_stable.py View 3 chunks +2 lines, -1 line 0 comments Download

Messages

Total messages: 1 (0 generated)
David James
10 years, 2 months ago (2010-10-22 00:26:45 UTC) #1
Per offline discussion with Sosa, this was already committed to fix the tree.
But sending a review in case you guys have ideas on a better way to do this.

We're thinking of just copying in the two functions we need from
portage.versions into our own library so that we don't add an extra dependency.

Powered by Google App Engine
This is Rietveld 408576698