crosutils: Revert "Cache sudo in make_factory_package"

This reverts commit 0126898d23afb00b04e05b51ea8b83c37aa49b0f.

When "sudo -v" is executed inside chroot, it prompts for password; however the
user account inside chroot may be using a different password (ex, "chronos")
from the same account outside chroot.  The /etc/sudoers file inside chroot has
explicitly specified "userid ALL=NOPASSWD: ALL" for the account, so we should
keep doing nothing inside chroot.

BUG=chrome-os-partner:2827
TEST=(inside chroot) ./make_factory_package --release ...... # success

Change-Id: Ibadd5d539df83d70aba0daabc40bb9edba842f07
Reviewed-on: http://gerrit.chromium.org/gerrit/7847
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
This commit is contained in:
Hung-Te Lin 2011-09-16 16:10:51 +08:00 committed by chrome-bot
parent de99e8b59a
commit 882cae5df4

View File

@ -175,9 +175,16 @@ setup_environment() {
OMAHA_DATA_DIR="${OMAHA_DIR}/static/${FLAGS_subfolder}/"
fi
echo "Caching sudo authentication"
sudo -v
echo "Done"
# When "sudo -v" is executed inside chroot, it prompts for password; however
# the user account inside chroot may be using a different password (ex,
# "chronos") from the same account outside chroot. The /etc/sudoers file
# inside chroot has explicitly specified "userid ALL=NOPASSWD: ALL" for the
# account, so we should do nothing inside chroot.
if [ ${INSIDE_CHROOT} -eq 0 ]; then
echo "Caching sudo authentication"
sudo -v
echo "Done"
fi
# Use this image as the source image to copy
RELEASE_DIR="$(dirname "${FLAGS_release}")"