| commit | 389634d71c1c037b69b339c9515cb849b402d645 | [log] [tgz] |
|---|---|---|
| author | Chris Sosa <sosa@chromium.org> | Wed Sep 05 19:56:53 2012 -0700 |
| committer | Chris Sosa <sosa@chromium.org> | Wed Sep 05 19:57:02 2012 -0700 |
| tree | 23ebe7845039e1b9f3d90bd254e9c5a5e4d0d793 | |
| parent | 15a884825af93f71e6e5b041923707d3b2e3d1cf [diff] [blame] |
Revert "Force our umount w/in the chroot." This change breaks the chromiumos_sdk builder. See http://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos%20sdk/builds/2314/steps/BuildBoard/logs/stdio This reverts commit 23da619f138d0b4ca148c3940ec8c4ff0827e396 Change-Id: I47aa6e94aa0c62494cc40e9964f25097d3353322 Reviewed-on: https://gerrit.chromium.org/gerrit/32349 Reviewed-by: Chris Sosa <sosa@chromium.org> Tested-by: Chris Sosa <sosa@chromium.org>
diff --git a/sdk_lib/enter_chroot.sh b/sdk_lib/enter_chroot.sh index 58cb0f5..77a25d4 100755 --- a/sdk_lib/enter_chroot.sh +++ b/sdk_lib/enter_chroot.sh
@@ -274,13 +274,9 @@ queue_mount /run/shm "--bind" /run/shm fi fi - # Get path overrides for the chroot in place now- it's possible - # that they may be needed for early teardown. - queue_mount "${FLAGS_trunk}/src/scripts/path-overrides" "--bind" \ - "/usr/local/path-overrides" - queue_mount "${FLAGS_trunk}" "--bind" "${CHROOT_TRUNK_DIR}" + debug "Setting up referenced repositories if required." REFERENCE_DIR=$(git config --file \ "${FLAGS_trunk}/.repo/manifests.git/config" \