Upgraded sys-apps/busybox to version 1.20.1 on amd64, arm, x86
Needed to work with newer kernel headers.
BUG=None
TEST=`emerge-amd64-generic busybox` worked
TEST=`emerge-x86-generic busybox` worked
Change-Id: I0806168726f02fc0312d2310efd657c2c0ccdb48
Reviewed-on: https://gerrit.chromium.org/gerrit/24759
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Craig Harrison <craigdh@chromium.org>
BUG=chromium-os:27493
TEST=Verify that packages are only rebuilt when their modification times
change (on either the ebuild or the content).
Change-Id: Iac44e86455d12601a25c8d02f14aa69a4829a330
Reviewed-on: https://gerrit.chromium.org/gerrit/24677
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Rather than having a toolchain package we use for the cross-compilers and
installing a different one for the target build dir, use the same package.
This makes updating more logical as we only have to do it in one place.
BUG=chromium-os:24928
TEST=`cbuildbot amd64-generic-full` works
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
TEST=build_packages+build_image for x86-alex boots & works
Change-Id: Ib083c3d2eae75d6f5437203990599cdc837dd9dc
Reviewed-on: https://gerrit.chromium.org/gerrit/24722
Reviewed-by: Anush Elangovan <anush@google.com>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
When bootstrapping a chroot, the test for "is this a private source
tree repo" looked under the source tree in ~/trunk/src. That test
was reliable inside the chroot (during update_chroot), but from
outside the chroot (during bootstrapping) it depended on whether the
user had a ~/trunk/src with a certain file.
This change enforces correct behavior outside the chroot regardless
of the contents of the user's home directory.
BUG=chromium-os:31602
TEST=run the test case described in the bug report
Change-Id: I2150347fbad9c84af537f8c572908e6e5ce312b4
Reviewed-on: https://gerrit.chromium.org/gerrit/24659
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Upgraded media-libs/libv4l to version 0.8.8 on amd64, arm, x86
BUG=None
TEST=Built using gcc-4.7
Change-Id: Iacb116f95ee7d07ea8baa6579e2cd7b716820646
Reviewed-on: https://gerrit.chromium.org/gerrit/24556
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Han Shen <shenhan@chromium.org>
Commit-Ready: Han Shen <shenhan@chromium.org>
The previous upgrade hook didn't change all the perms on files in the host
distdir because the default value expands to a symlink which `find` did not
walk. Add the -H flag to make that happen.
For people who haven't upgraded yet, stub out the existing 38 hook.
BUG=chromium-os:3616
TEST=add a root owned file to host distdir, run ./update_chroot, see file owners fixed
Change-Id: I3f5f88b4fb1d27ce588a342331ad10e957961bcc
Reviewed-on: https://gerrit.chromium.org/gerrit/24459
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Users of other calling scripts that no-op in this scripts are seeing
the warning message incorrectly. Moving this message further down
avoids this issue.
BUG=None
TEST=Visual. Also using to test unified commit queue.
Change-Id: I7bc227f37b26bcedbdb8214286a3f8646ddb610c
Reviewed-on: https://gerrit.chromium.org/gerrit/24369
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
Upgraded sys-power/powertop to version 2.0 on amd64, arm, x86
This one fixes building with gcc-4.7.
BUG=None
TEST=`emerge-amd64-generic powertop` worked
TEST=`emerge-arm-generic powertop` worked
TEST=`emerge-x86-generic powertop` worked
Change-Id: I5abdb5e03b822efe8757e80bb9c4dbf3526d72ab
Reviewed-on: https://gerrit.chromium.org/gerrit/24311
Reviewed-by: Han Shen <shenhan@google.com>
Reviewed-by: Han Shen <shenhan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Now that we're enabling userpriv for the chroot, we need to fix all the
paths that might be owned by root to the right user.
BUG=chromium-os:3616
TEST=`./update_chroot` on a system with root-owned files
in the various paths changed them all to my user
Change-Id: I3655c851d5844524ec77c3476cee7a6e9d70ce0d
CQ-DEPEND=Id513c0b8b380d57dd3e150917a969d0bf36883fc
Reviewed-on: https://gerrit.chromium.org/gerrit/24216
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=`emerge-amd64-generic gmock` worked
TEST=`emerge-arm-generic gmock` worked
TEST=`emerge-x86-generic gmock` worked
Change-Id: Iccc6379d5e814ad959d077d78efbf2c6aa4ca364
Reviewed-on: https://gerrit.chromium.org/gerrit/24063
Reviewed-by: Han Shen <shenhan@google.com>
Reviewed-by: Han Shen <shenhan@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:19287
TEST=try building a chroot both using .tbz2, .tar.bz2 and .tar.xz
Change-Id: Idfb13b691201b65c1fa1d5f8597f2aaa401a4051
Reviewed-on: https://gerrit.chromium.org/gerrit/23964
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
With the migration to cros_setup_toolchains, we no longer pass down the
versions of binutils/gcc/etc..., so drop the explicit flags.
BUG=chromium-os:23032
TEST=`cbuildbot x86-generic-full` works
Change-Id: I87dbb449e3c413c44cd008fc43d3258a2111227b
Reviewed-on: https://gerrit.chromium.org/gerrit/24056
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded sys-kernel/linux-headers to version 3.4 on amd64, arm, x86
BUG=chromium-os:28936
TEST=`cbuildbot chromiumos-sdk` worked
Change-Id: I6caeb19e04dac09385e56d72955ff140ca44db72
Reviewed-on: https://gerrit.chromium.org/gerrit/20494
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Anush Elangovan <anush@google.com>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
This has new features we want (--init-target / --env).
BUG=chromium-os:31348
TEST=`cbuildbot chromiumos-sdk` worked
Change-Id: Idd27b2aa78fd965e210dece215a45e401ea355a7
Reviewed-on: https://gerrit.chromium.org/gerrit/23940
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Use the ":" builtin command to prevent the increment of $ERROR_COUNT from
ever failing under strict mode (i.e. "set -e").
cros_generate_breakpad_symbols failed for some reason, and this is my best
guess as to the cause. That is, the post-increment would otherwise fail
when $ERROR_COUNT is zero because it would have a non-zero exit status.
BUG=chromium-os:31332
TEST=Manually ran script
Change-Id: Iec7fd9358c339414ccd3c2ca1fd598f124375f0b
Reviewed-on: https://gerrit.chromium.org/gerrit/23979
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Require hashes to be available for downloaded files.
BUG=chromium-os:24209
TEST=`cbuildbot amd64-generic-full` worked
TEST=`cbuildbot arm-tegra2-full` worked
TEST=`cbuildbot x86-generic-full` worked
Change-Id: I915c4a5107033cc22f9c9fc79ff0d2d3daeea6fb
CQ-DEPEND=I7645654abf104b620e646448595766c4d67161c3
Reviewed-on: https://gerrit.chromium.org/gerrit/22852
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
For the builders/goobuntu, they're running pbzip2 ~1.0.5 w/ tar 1.22;
for whatever reason, that configuration reproducibly limits to single
core for:
tar -I /usr/bin/pbzip2 -xf /the/sdk
This is annoying; 2 minutes instead of 10s for 48 core builder for
example. Thus does *not* occur w/in the chroot (differing versions),
nor for tar=1.26 w/ pbzip2 1.1.6. The changelogs for both programs
are a bit spartan, but I'm suspecting tar just wasn't feeding it
particularly well (pbzip2 1.0.5 will parallelize if stdin is a pipe).
Regardless, we either try to force everyone to upgrade, or we just
use a form that behaves fine, which is what this CL does.
BUG=chromium-os:31320
TEST=manual validation of it.
Change-Id: I77a434bd2c70873459cbf373192fe73feadb2547
Reviewed-on: https://gerrit.chromium.org/gerrit/23811
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
We need to rebuild binpkgs that depend on openssl.
Change-Id: I13c59a79700e5704b463b7d03ffbf19d83c5e2e7
Signed-off-by: Elly Jones <ellyjones@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/23743
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: David James <davidjames@chromium.org>
This one includes fixes for building with glibc-2.15+.
BUG=None
TEST=`qlist -Iv` worked
TEST=`emerge-x86-alex pambase` worked
Change-Id: Ifeed2fef275a3b59fe35e7454239f3035b80d508
Reviewed-on: https://gerrit.chromium.org/gerrit/23744
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Looks like we had some manual bumps that didn't update the Manifest
files, so do that now to get complete coverage.
BUG=chromium-os:24209
TEST=`cbuildbot amd64-generic-full` worked
TEST=`cbuildbot arm-tegra2-full` worked
TEST=`cbuildbot x86-generic-full` worked
Change-Id: Ie41ee84104aaf0965f820acfe49476ad9ebc3f80
Reviewed-on: https://gerrit.chromium.org/gerrit/23572
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
We'll phase out later.
BUG=chromium-os:31183
TEST=Ran it.
Change-Id: I7ddf44b661f52ca9186e429ed3955884c4b2cbd4
Reviewed-on: https://gerrit.chromium.org/gerrit/23653
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
Upgraded dev-python/pyinotify to version 0.9.3 on amd64
BUG=None
TEST=emerged into chroot
Change-Id: I997914de25bc90e3cf660769f487bcebc37d4ae3
Reviewed-on: https://gerrit.chromium.org/gerrit/23602
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Jon Salz <jsalz@chromium.org>
Tested-by: Jon Salz <jsalz@chromium.org>
This includes a fix for building with gcc-4.7.
BUG=None
TEST=`emerge ctemplate` works
TEST=`emerge-amd64-generic ctemplate` works
TEST=`emerge-arm-generic ctemplate` works
TEST=`emerge-x86-generic ctemplate` works
Change-Id: I8752fc23fc1e636c59fc11eee2ee75a5f826ab7b
Reviewed-on: https://gerrit.chromium.org/gerrit/23543
Reviewed-by: Han Shen <shenhan@google.com>
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Han Shen <shenhan@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
This includes a fix for building with gcc-4.7.
BUG=None
TEST=`emerge gtest` works
TEST=`emerge-amd64-generic gtest` works
TEST=`emerge-arm-generic gtest` works
TEST=`emerge-x86-generic gtest` works
Change-Id: I65984c3b362be2ae3fbc3ec0f7d4fdfd939f361d
Reviewed-on: https://gerrit.chromium.org/gerrit/23357
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Han Shen <shenhan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Remove libdrm 2.4.32 from portage-stable, it's been replaced by libdrm
2.4.24 in chromiumos-overlay. Upgrade xf86-video-nouveau, as it is no
longer compatible with libdrm 2.4.34.
BUG=chromium-os:31134
TEST=Tested on lumpy
Change-Id: I1f219bd1df1d3041c98b74ee386b824c510c16ad
awdf
Change-Id: Ic433ed668822292d08edec81f2e2778f87d28091
Reviewed-on: https://gerrit.chromium.org/gerrit/23538
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Ready: Sean Paul <seanpaul@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
Add the upstream ebuild for openssl 0.9.8x. We only need this because the
netflix plugin links against 0.9.8 specifically, and we're about to go to
1.0.1c.
BUG=chromium-os:21100
TEST=build_image
Change-Id: Iac12a26dca84fb40e5e07d26f409531ac65035d4
Signed-off-by: Elly Jones <ellyjones@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/23379
Reviewed-by: Mike Frysinger <vapier@chromium.org>
We are about to separate VFAT support from 'initramfs' flag. Let's add
'vfat' flag first so that when this happens nothing gets broken.
BUG=chrome-os-partner:9805
TEST=Build success. Factory install shim still works.
Change-Id: Ia432e3b1a6186f4f7c817a1283c86066ced5fef1
Reviewed-on: https://gerrit.chromium.org/gerrit/23193
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
This one won't run docbook tools, so won't try and hit the network.
BUG=chromium-os:31096
TEST=`emerge-amd64-generic gpsd` works
TEST=`emerge-arm-generic gpsd` works
TEST=`emerge-x86-generic gpsd` works
TEST=`cbuildbot {amd64,arm,x86}-generic-full` worked
Change-Id: I131f33acadeef5aa427ad0c6a380188bb3920773
Reviewed-on: https://gerrit.chromium.org/gerrit/23226
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upgraded dev-python/m2crypto to version 0.21.1 on amd64, arm, x86.
Needed for openssl-1.0 upgrade.
BUG=None
TEST=`emerge m2crypto` works
TEST=`emerge-amd64-generic crda` works (its build code calls m2crypto)
Change-Id: I821f4bb8fb905227df79076052b82a339a34c539
Reviewed-on: https://gerrit.chromium.org/gerrit/23259
Reviewed-by: Elly Jones <ellyjones@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The opensc code doesn't link against -ldl itself, so it'll fail to link
when openssl fixes itself to stop spewing -ldl implicitly.
This has been fixed upstream, so pull down that fix.
BUG=None
TEST=`emerge-x86-alex opensc` still works
Change-Id: I1c53912afcb0e7830f056000b7ba0f72b7562ae7
Reviewed-on: https://gerrit.chromium.org/gerrit/23253
Reviewed-by: Elly Jones <ellyjones@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded dev-util/lcov to version 1.9 on amd64
BUG=chromium-os:31178
TEST=Package emerges correctly on host
Change-Id: Iaec47e65cb1c8283cda2805ff9cdc7e2294e8e21
Reviewed-on: https://gerrit.chromium.org/gerrit/23237
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Turns out we do not need fakeroot after all.
This reverts commit 0d5287dfe37e1ed15b2ac402997eb9d11e06bda7
Change-Id: I8130bc2aac308bfa678a90cd8586242df9006615
Reviewed-on: https://gerrit.chromium.org/gerrit/23234
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Commit-Ready: Gilad Arnold <garnold@chromium.org>
At present if a download fails, we don't report this in the return code.
This means there is no indication of failure to cros_bundle_firmware.
Correct the return code in this case, with a new patch.
BUG=chrome-os-partner:9633
TEST=manual:
$ cros_bundle_firmware -b daisy -w usb --bl1 <fname>
where fname is an old BL1 which breaks USB download.
See that the failure to download BL2 is now reported and
cros_bundle_firmware stops with an error.
Change-Id: I3bb966bf3c1a9009cfba4064da872a8dd8cb6043
Reviewed-on: https://gerrit.chromium.org/gerrit/23145
Reviewed-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Make shill and flimflam ignore pseudomodem0p on test builds so that
the network devices called pseudomodem0p can be used to test the
cellular classes of shill on virtual machines.
BUG=none
TEST=run network_3GModemControl on a vm
Change-Id: I61cc89d114dcb82bb01b864b68f220fbaf21509d
Reviewed-on: https://gerrit.chromium.org/gerrit/23059
Commit-Ready: Jason Glasgow <jglasgow@chromium.org>
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Tested-by: Jason Glasgow <jglasgow@chromium.org>
We need VFAT, ramdisk, and frame buffer console in network boot kernel.
BUG=chrome-os-partner:9805
TEST=Build success. Network boot and install success.
Change-Id: I267f305e2cedf44d002bb1acdf790b4279e20f2c
Reviewed-on: https://gerrit.chromium.org/gerrit/23196
Commit-Ready: Vic Yang <victoryang@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
This package is currently unused but will be used by update_engine.
BUG=chromium-os:31088, chromium-os:31089
TEST=emerge it.
Change-Id: I2df3d2a0c72d258cf60ec43e1d55ff0c330daaf5
Reviewed-on: https://gerrit.chromium.org/gerrit/23089
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Commit-Ready: David James <davidjames@chromium.org>
Now that this is part of hard-host-depends, an we don't build the chroot
itself with ccache, so there's no need to force it in early.
BUG=None
TEST=`cbuildbot chromiumos-sdk` passed
Change-Id: I8b7c2a8c6f6df5eedac0c06ebb847f3011eb86d0
Reviewed-on: https://gerrit.chromium.org/gerrit/22954
Reviewed-by: Anush Elangovan <anush@google.com>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Current make_netboot.sh only supports ARM. As we are using network boot
for x86 now, let's fix make_netboot.sh to support both.
BUG=chrome-os-partner:9805
TEST=Generates images and network boot install shim.
Change-Id: Ib445f68255fe8e8a1ee6b7901c9bd67a4a36636d
Reviewed-on: https://gerrit.chromium.org/gerrit/23010
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Commit-Ready: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
Running these as root does not make sense. Furthermore, it will fail
on calling cros-workon, which sometimes fails but most certainly will
not give correct information anyway.
BUG=chromium-os:30384
TEST=run build_packages/setup_board with/without sudo
Change-Id: I0cba72334369e35ba0e864c53fd81037ee9e0efa
Reviewed-on: https://gerrit.chromium.org/gerrit/23003
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
When bootstrapping for the first time, files in chroot/etc/ might not
exist, so we can't run `find` on them. This manifests itself currently
by spitting out the warning on all initial sdk boots:
find: `.../chroot/etc/resolv.conf': No such file or directory
People can find this confusing and cause sheriffs to waste time on the
wrong thing, so rework the code to avoid this.
BUG=None
TEST=`cros_sdk --delete ; cros_sdk` no longer warns about resolv.conf
Change-Id: I83f892e325e63e682aeb370a9dfc33e284e059d2
Reviewed-on: https://gerrit.chromium.org/gerrit/22845
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upgraded sys-fs/mtd-utils to version 1.4.8 on amd64, arm, x86.
We want it for some simple testing. Nothing pulls it in yet.
BUG=None
TEST=`emerge-amd64-generic mtd-utils` works
TEST=`emerge-arm-generic mtd-utils` works
TEST=`emerge-x86-generic mtd-utils` works
Change-Id: I5b385e3fe2d491936be12db0da3ae28a02a5d397
Reviewed-on: https://gerrit.chromium.org/gerrit/22822
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Bryan Freed <bfreed@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Since /etc/mtab could be stale, use /proc/mounts instead.
BUG=None
TEST=`cros_sdk` in diff terminals still works
Change-Id: I526e5173581820c6983fe3702493a0349c1232c3
Reviewed-on: https://gerrit.chromium.org/gerrit/22860
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Looks like we had some manual bumps that didn't update the Manifest
files, so do that now to get complete coverage.
BUG=chromium-os:24209
TEST=`cbuildbot amd64-generic-full` worked
TEST=`cbuildbot arm-tegra2-full` worked
TEST=`cbuildbot x86-generic-full` worked
Change-Id: I7645654abf104b620e646448595766c4d67161c3
Reviewed-on: https://gerrit.chromium.org/gerrit/22851
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Resubmit of If62b4f3973f02fd8e1deed35864c824a02ab0c22
This will be safe to land after
I2c4e21ec7e8c0c0cf58947e2b0a3a9edf7617a09
The breakage was a timing issue paired with people not always syncing
the complete tree. No changes to the CL are needed.
It is now used for:
- make_chroot (cros_sdk --bootstrap)
- update_chroot
setup_board is stripped of redundant code which was deprecated by this.
Also stripped is some usepkg logic in make_chroot, as that is now
exclusively source-only.
BUG=chromium-os:23032
TEST=trybot chromiumos-sdk
Change-Id: Ib888cf2886218622d9cfeebb17b9cd4462d06c89
Reviewed-on: https://gerrit.chromium.org/gerrit/22578
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
