3 Commits

Author	SHA1	Message	Date
Brian Harring	f264b82dd2	Force our umount w/in the chroot. ... Do this via ensuring that any common.sh invoker of raw umount (say a root script) sees our umount path. Additionally, inject into default profiles our override, and via an upgrade scriptlet. This is round two; originally appeared as CL:32088, was reverted due to: https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos%20sdk/builds/2314/steps/BuildBoard/logs/stdio The fix however is just adding a single sudo mkdir. :/ BUG=chromium-os:23443 TEST=cros_sdk --replace --bootstrap TEST=cros_sdk --replace Change-Id: I0dc7522a9c623f40081d4f138cea0c2c45171fea Reviewed-on: https://gerrit.chromium.org/gerrit/32365 Commit-Ready: Brian Harring <ferringb@chromium.org> Tested-by: Brian Harring <ferringb@chromium.org> Reviewed-by: Chris Sosa <sosa@chromium.org>	2012-09-06 10:34:33 -07:00
Chris Sosa	389634d71c	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>	2012-09-05 19:57:02 -07:00
Brian Harring	23da619f13	Force our umount w/in the chroot. ... Do this via ensuring that any common.sh invoker of raw umount (say a root script) sees our umount path. Additionally, inject into default profiles our override, and via an upgrade scriptlet. BUG=chromium-os:23443 TEST=manual validation, trybot. Change-Id: Ie2514f6e8d2e10a19ab8d11c8056177bc1a2fb4d Reviewed-on: https://gerrit.chromium.org/gerrit/32088 Reviewed-by: Mike Frysinger <vapier@chromium.org> Commit-Ready: Brian Harring <ferringb@chromium.org> Tested-by: Brian Harring <ferringb@chromium.org>	2012-09-05 14:38:14 -07:00